[MEI-L] Describing composite sources

Wed Dec 1 16:46:20 CET 2010

Axel,

Indeed, <relateditem> is very powerful so I think it should be implemented in the next release of the schema. :)  The fact that it can be (mis|ab)used shouldn't stop its inclusion.

In the meantime, I'll send you an ad hoc extension of the schema (in RNG) that you can play with now.  It will be great to have you test it so we can identify any problems before the release.

--
p.

__________________________
Perry Roland
Music Library
University of Virginia
P. O. Box 400175
Charlottesville, VA 22904
434-982-2702 (w)
pdr4h at virginia.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: Wednesday, December 01, 2010 10:33 AM
To: Music Encoding Initiative
Subject: Re: [MEI-L] Describing composite sources

Hi Perry

Thanks. Just to make sure I understand: You suggest simply extending the schema ad hoc with an extra element? That is quite a trick. Or is it planned to be implemented in a future version of MEI anyway? I would be very reluctant to start customizing the schema for individual needs.
On the other hand, relateditem is obviously quite a powerful (or dangerous, if you like) solution, which actually may be able to solve some even bigger problems like tying together different versions of a given piece (e.g. some incidental music from which extracts are published separately as a suite, or music rearranged for other instruments). We consider using meicorpus for that purpose (by interpreting "corpus" as "the totality of versions that constitute a work" - but that interpretation may be questionable and also precludes us from using meicorpus in a more "physical" sense). Relateditem may turn out to be a better approach. I'll have to think about  that, and would be happy to hear other opinions as well.

/axel

-----Oprindelig meddelelse-----
Fra: mei-l-bounces at lists.uni-paderborn.de [mailto:mei-l-bounces at lists.uni-paderborn.de] På vegne af Roland, Perry (pdr4h)
Sendt: 1. december 2010 15:46
Til: Music Encoding Initiative
Emne: Re: [MEI-L] Describing composite sources

Hi, Axel,

I've also run into problems with composite sources while trying to describe a publication that contains multiple chansons.  What was needed was a way to create a title statement for each chanson.

The solution is to add a <relateditem> element within <source> with a content model that is essentially the same as <source>.  This will allow the description of constituent intellectual or physical parts of the source.

The following RNG fragment fits the bill --

<define name="relateditem">
<element name="relateditem">
<a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0">relateditem ― contains or references another bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it. This element is modelled on the relatedItem element in the Text Encoding Initiative (TEI) and MODS schemas.</a:documentation> <zeroOrMore xmlns:rng="http://relaxng.org/ns/structure/1.0" xmlns:sch="http://purl.oclc.org/dsdl/schematron">
<ref name="model.identifierLike"/>
</zeroOrMore>
<optional>
<ref name="titlestmt"/>
</optional>
<optional>
<ref name="editionstmt"/>
</optional>
<optional>
<ref name="pubstmt"/>
</optional>
<optional>
<ref name="physdesc"/>
</optional>
<optional>
<ref name="seriesstmt"/>
</optional>
<optional>
<ref name="notesstmt"/>
</optional>
<optional>
<ref name="langusage"/>
</optional>
<optional>
<ref name="classification"/>
</optional>
<zeroOrMore xmlns:rng="http://relaxng.org/ns/structure/1.0" xmlns:sch="http://purl.oclc.org/dsdl/schematron">
<ref name="extref"/>
</zeroOrMore>
<zeroOrMore xmlns:rng="http://relaxng.org/ns/structure/1.0" xmlns:sch="http://purl.oclc.org/dsdl/schematron">
<ref name="relateditem"/>
</zeroOrMore>
<ref name="att.datapointing.attributes"/>
<ref name="att.common.attributes"/>
<ref name="att.bibl.attributes"/>
<optional>
<attribute name="rel">
<a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"/>
<choice>
<value>preceding</value>
<a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"/>
<value>succeeding</value>
<a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"/>
<value>original</value>
<a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"/>
<value>host</value>
<a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"/>
<value>constituent</value>
<a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"/>
<value>separatedMaterial</value>
<a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"/>
<value>otherVersion</value>
<a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"/>
<value>otherFormat</value>
<a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"/>
<value>isReferencedBy</value>
<a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"/>
<value>references</value>
<a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"/>
</choice>
</attribute>
</optional>
<empty/>
</element>
</define>

The n attribute on relateditem could be used to assign a label to the constituent part being described if <titlestmt> isn't used.

This solution opens up a whole new range of possibilities for (mis|ab)use so please use it with caution.

Comments and questions welcomed.

--
p.

__________________________
Perry Roland
Music Library
University of Virginia
P. O. Box 400175
Charlottesville, VA 22904
434-982-2702 (w)
pdr4h at virginia.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: Wednesday, December 01, 2010 5:47 AM
To: Music Encoding Initiative
Subject: [MEI-L] Describing composite sources

Dear all

When coding source descriptions we are facing some problems with composite sources, i.e. sources consisting of more than one type of paper. Adding several <physmedium>, <dimensions>, <extent> and <handlist> elements to <physdesc> is no problem, but how can we the group the information to show which dimensions refer to which physmedium etc.? I am not convinced that relying on the simple sequence of elements is enough to avoid ambiguity. Also, it would be nice if some description of contents such as "bars 12-46" or "first movement" could be attached to such a group of physical features to explain what part of the piece is contained in which part of the source. Any ideas, anyone?

All the best,
Axel

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 | 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
_______________________________________________
mei-l mailing list
mei-l at lists.uni-paderborn.de
https://lists.uni-paderborn.de/mailman/listinfo/mei-l