[MEI-L] <work> metadata questions
Roland, Perry (pdr4h)
pdr4h at eservices.virginia.edu
Mon Aug 29 17:10:30 CEST 2011
Hi Axel,
Thanks for testing this out and providing feedback. It's a huge help.
I don't think you should ever have to use <scoredef> to record metadata so I'll make additions to the descriptive elements allowed in <source>, <relatedItem> and <work>. I'll also try to clarify the relationships between <castList> and <perfMedium> and between <contents> and <relatedItem>, and tweak <incip> a bit to make it, as you say, "more elegant".
I think these changes are minor and can be accomplished for the next release. I'm working on something else right now, but I should be able to get something out for testing in the next couple of weeks.
--
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 Axel Teich Geertinger [atge at kb.dk]
Sent: Thursday, August 11, 2011 5:32 AM
To: Music Encoding Initiative
Subject: [MEI-L] <work> metadata questions
Hi Perry & all
I am trying to translate our existing metadata model to the new MEI header elements within <workDesc>. Huge improvements, thank you!!
Still, however, I cannot figure out how to completely avoid using <score> for some metadata, especially when getting down to movement level. And I have some other questions too (see below).
This is a first shot at outlining the first movements of a piece for orchestra, chorus and vocal soloists:
<work>
<key pname="a" mode="minor"/> <!-- @accid missing? Only @accid.ges seems to be available -->
<perfMedium>
<ensemble>
<instrVoice>Orchestra</instrVoice>
</ensemble>
<ensemble>
<instrVoice>Choir SSATTBB</instrVoice>
</ensemble>
<performer> <!-- How does <perfomer> relate to <castItem>? -->
<instrVoice>S</instrVoice>
<role>Comala</role>
</performer>
<performer>
<instrVoice>Bar</instrVoice>
<role>Fingal</role>
</performer>
</perfMedium>
<castList>
<castItem>
<role>Comala</role>
<roleDesc xml:lang="de">Fingals Geliebte</roleDesc>
<roleDesc xml:lang="da">Fingals elskede</roleDesc>
</castItem>
<castItem>
<role>Fingal</role>
<roleDesc xml:lang="de">König von Morwen</roleDesc>
<roleDesc xml:lang="da">Konge af Morven</roleDesc>
</castItem>
</castList>
<contents>
<head>
<title xml:lang="de">Akt 1</title>
<title xml:lang="da">Akt 1</title>
</head> <!-- Only one <head> allowed, i.e. no way to add "Akt 2" heading, etc.? -->
<contentItem> <!-- How are these items linked to their respective elements in <music>? Using @analog? -->
<title xml:lang="de">No. 1. Chor der Krieger und Barden [TTBB]</title>
<title xml:lang="da">No. 1. Fingals Krigere</title>
<!-- No way to use <key> and <tempo> anywhere here? -->
<!-- And how about a <meter> element? -->
<incip>
<p xml:lang="de">Auf, auf, auf, laut schallt das Horn</p>
<p xml:lang="da">Frem, frem, frem, fremad til Kamp</p>
<p label="graphics"> <!-- container for links to incipit graphics -->
<extptr targettype="lowres" mimetype="image/png" xl:href="http://img.kb.dk/..."/>
<extptr targettype="hires" mimetype="image/png" xl:href="http://img.kb.dk/..."/>
</p>
<score>
<app>
<rdg type="metadata">
<!-- Declared in a "metadata" reading in order to avoid conflict with an actual encoding of the incipit -->
<scoreDef key.pname="a" key.accid="n" key.mode="minor" meter.sym="common"/> <!-- key and meter at movement level -->
<staff><layer><tempo>Andante – Allegro non troppo</tempo></layer></staff> <!-- tempo indications in this movement -->
</rdg>
</app>
</score>
</incip>
</contentItem>
<contentItem>
<title xml:lang="de">No. 2 [Comala, Fingal]</title>
<title xml:lang="da">No. 2 [Comala, Fingal]</title>
<incip>
<p xml:lang="de">Heute noch brech' ich des stolzen Königs Macht</p>
<p xml:lang="da">Alt i Kvæld slaar jeg den stolte Konges Hær</p>
<p label="graphics">
<extptr targettype="lowres" mimetype="image/png" xl:href="http://img.kb.dk/..."/>
<extptr targettype="hires" mimetype="image/png" xl:href="http://img.kb.dk/..."/>
</p>
<score>
<app>
<rdg type="metadata">
<scoreDef key.pname="e" key.accid="n" key.mode="major" meter.sym="common"/>
<staff><layer><tempo>Andante – Più lento – Andante con moto</tempo></layer></staff>
</rdg>
</app>
</score>
</incip>
</contentItem>
</contents>
</work>
As you can see, I have marked some questions in the example:
1) Isn’t the accid attribute missing in the definition of <key>? I only see @accid.ges.
2) Some of the <performer> and <castItem> elements should be linked somehow to indicate that they refer to the same role. How?
3) Would it be possible to allow more than one <head>, so that it could be used as headings for subsequent acts, for instance? Or am I doing something wrong? (Actually the piece in the example does not have any acts, I just included the heading for testing purposes)
4) How do I indicate the relation between <contentItem> elements and their corresponding sections in <music>?
5) Could <key> be available in <contentItem> to indicate key at movement level? Both for key and for tempo, I still need to define <scoreDef> and <staff> elements, don’t I? As I want key and tempo to actually record information about the entire movement, not just the incipit, they should not be placed within the <incipit> at all, but rather directly under <contentItem>. And how about a <meter> element too? I would like to see <key>, <tempo> and perhaps <meter> to be available as children of both <work> and <contentItem> - or are there good reasons not to have them? There probably are :-) I am aware that “key” may refer both to an indication of key at some particular point in the score as well as the more abstract conception of key for an entire movement or piece. The same may not be true with meter, or at least not completely in the same sense. Tempo however, like key, may also indicate a change of tempo at some point or informing about the sequence of tempos in the piece (“Andante – Più lento – Andante con moto”). And since <key> _will_ be implemented in this “metadata” manner, I think it could would be acceptable to do the same with tempo and meter.
6) Is there a more elegant way of linking to incipit graphic files than using <extptr> within a <p>?
Sorry for asking all these questions. But in case some of them may actually turn out to have any influence on the next release, I thought it would be all right to bother you with them now :-)
All the best,
Axel
[http://support.kb.dk/images/kb_logo.jpg]
Det Kongelige Bibliotek
Nationalbibliotek og Københavns Universitetsbibliotek
Axel Teich Geertinger
Forsker | Researcher
Det Kongelige Bibliotek | The Royal Library
Dansk Center for Musikudgivelse | Danish Centre for Music Publication
P.O. Box 2149 | DK-1016 København K
tel +45 3347 4706 | Fax +45 3393 2218 | atge at kb.dk<mailto:atge at kb.dk> | www.kb.dk<http://www.kb.dk>
Besøgsadresse | Visiting address | Søren Kierkegaards Plads 1
Leveringsadresse | Delivery address | Christians Brygge 8 | 1219 København K
EAN 5798 000 79 52 97 | Bank 0216 4069032583 | CVR 28 98 88 42
IBAN DK2002164069032583 | Swiftcode DABADKKK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20110829/dbc7703c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 14433 bytes
Desc: image001.jpg
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20110829/dbc7703c/attachment.jpg>
More information about the mei-l
mailing list