[MEI-L] instrumentation in header

[Roland, Perry (pdr4h)]

Hi Axel, Joachim, everyone,

Sorry for the delay in answering -- I thought I hit the send button 2 days ago, but since my answer hasn't come through, I suppose I didn't.

Anticipating the need for such things, a <perfMedium> element has already been added.  This element is based on the MARC 048 tag (at least I think it was 048).  This element is allowed in <sourceDesc>, <work>, and <relatedItem>.

Hope this helps,

--
p.

__________________________
Perry Roland
Music Library
University of Virginia
P. O. Box 400175
Charlottesville, VA 22904
434-982-2702 (w)
pdr4h (at) virginia (dot) edu
________________________________
From: mei-l-bounces at lists.uni-paderborn.de [mei-l-bounces at lists.uni-paderborn.de] on behalf of Joachim Veit [veit at weber-gesamtausgabe.de]
Sent: Wednesday, July 20, 2011 12:47 PM
To: mei-l at lists.uni-paderborn.de
Subject: Re: [MEI-L] instrumentation in header

Dear Axel and all,
I heavily agree with Axel concerning the wish for an <instrumentList> in the header which would make it much easier for us in doing a sort of "simple cataloguing" of works: When we try to list the instruments of an opera, for instance, we do that in the moment (following Axel's model) in the scoreDef with staffGroup(s) - but in an opera there are changing instrumentations in each number, so we misuse this scoreDef as a "collective" form of listing all the instruments ever playing somewhere in the work. This is clearly the task of such an "instrumentList" which besides would make it easier to use a more abridged way of catalogue-encoding in the header.
Concerning incip I too would prefer to add the "it" at the end because "it" would not make any weighing machine complain?
And many thanks to you, Axel, for taking part in our discussions in the Virtual Meeting!!!
Best greetings,
Joachim
P.S. In a few minutes we shall make "it" - that's to say: start to drink a bee(r)!


Am 20.07.11 17:58, schrieb Axel Teich Geertinger:
Dear all,

first of all thank you for the excellent virtual meeting! I really enjoyed hearing you all and even seeing some of you :-)

I have a question to the tech team: Now that we will soon have elements like <incip>, <key> and <castList> in the header, why not also add something like <instrumentList>? What these metadata have in common is that they are actually also contained in the score, although in a more or less “hidden” way, perhaps (as with key) requiring some analysis or interpretation.
Very much like the cast list, a list of instruments could in principle be harvested from a complete encoded score. In our cataloguing projects, however, the scores are not necessarily available, so we need to add that information either as a note somewhere in the header or in a staffDef, which does nothing but defining the instruments involved (a solution I would be happy to get rid of). The incipit will not do, as in many cases not all instruments will appear in it.
The same problem is true with choirs and vocal soloists, when they do not represent a named character and therefore will not fit into the castList.

Another question: why <incip>, and not <incipit>? We have quite long element names like <classification>, so why abbreviate incipit?

All the best,
Axel



_______________________________________________
mei-l mailing list
mei-l at lists.uni-paderborn.de<mailto:mei-l at lists.uni-paderborn.de>
https://lists.uni-paderborn.de/mailman/listinfo/mei-l


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20110722/e7acdfa8/attachment.html>