[MEI-L] relateditem and relations between mei elements

[Eleanor Selfridge-Field]

Hi, Axel,



I constructed a typology for source  “variants” in my contribution
“Musical Variants in Digital Practice” to Digitale Edition zwischen
Experiment und Standardisierung (Peter Stadler und Joachim Veit, eds.,
Niemeyer 2009).



In it I considered variants that pertain to scores (and parts) at four
levels of granularity: (1) note-level variants, (2) note-group and
phrase-level variants, (3) part-level and/or orchestral variants, and (4)
tree-structure variants. (This typology accommodates variant editorial
readings up to a point.)



Because there were some difficulties with one of the figures in the
circulated version, I am attaching the final edit version here (for
MEI-group use only).



For durable code structures, one really needs to accommodate “variants” at
whatever level suits the repertory at hand. I am sure there are situations
in which all of the above occur together.



·         (1) Provisions for note-level variants should usually work for
monophonic repertories, but one can easily conjure up exceptions
(folk-song repertories with translated texts that change syllabification
and add or subtract notes in arbitrary numbers).

·         (2)Note-group and phrase-level variants need to operate on the
second tier for repertories that have beams and slurs, which means most
repertories from 1600 on and quite a bit from before that time.

·         (3) Variations in voicing, instrumentation, instrument grouping,
et al., reflect the steady improvements in printing from the eighteenth
century onward.

·         (4) Tree-structure variants are rampant in manuscript studies
where multiple versions exist (or are reflected—as they often are in
Handel and Vivaldi—by writing them into margins).



Thinking in the first two levels is also useful for handling some
articulations (such as trills, which consume time but do not appear to do
so on the page) and basso continuo figuration. 1:1 (note-level) works in
some situations but not in all.



A “just enough” scheme for MEI markup (i.e., use Level 1 where it works
throughout the piece, default to it from higher levels within more complex
pieces) would have much to recommend it.



Since a lot of music at the Danish National Library site (which I value
for its transparent organization: thanks!!) come from the eighteenth and
nineteenth centuries, I believe that its interests would be well served
from the ability to accommodation Levels 1, 2, and 3.



Eleanor





Eleanor Selfridge-Field

Stanford University

Stanford, CA 94305-3076

USA

http://www.stanford.edu/~esfield/

http://www.ccarh.org









From: mei-l-bounces at lists.uni-paderborn.de
[mailto:mei-l-bounces at lists.uni-paderborn.de] On Behalf Of Axel Teich
Geertinger
Sent: Wednesday, January 05, 2011 9:51 AM
To: Music Encoding Initiative
Subject: [MEI-L] relateditem and relations between mei elements



Hi Perry (& others who might be interested)



I’ve been testing <relatedItem> to describe composite sources, and it
seems to do the job nicely.

However, I have also been trying for some time to figure out how to model
relations not just between sources (and parts of sources), but between
different versions of a work – i.e. encodings which may have several
sources each. How should I model the relation between, say, some
incidental music, encoded in one MEI file, and some excerpt or arrangement
encoded in another MEI file?

I noticed that one of the relations possible in <relatedItem> is
“otherVersion”. That’s exactly what I was looking for, except that it
needs to be on a higher level than <source> (because it relates to all the
sources to this particular version). One solution could be using <extptr>;
something like



    <filedesc>
      <notesstmt>
        <annot type="links">
          <extptr xl:role="isVersionOf" xl:href="..."/>
        </annot>
      </notesstmt>
    </filedesc>



Any better ideas? I am not sure <notesstmt> is the best place for this
type of information.



Happy new year to all!

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 |  <mailto:atge at kb.dk> atge at kb.dk |
<http://www.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



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20110105/d2dec86a/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 14433 bytes
Desc: not available
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20110105/d2dec86a/attachment.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Padernborn__v3_Mar2009.pdf
Type: application/pdf
Size: 634626 bytes
Desc: not available
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20110105/d2dec86a/attachment.pdf>