Add a new element to mark the presence of music notation, describe it and point to an external representation and/or embed an XML-based representation. Possible names are musicNotation (if request #3086720 is accepted) or musicalNotation, etc.
Module and Classes:
Music notation embedded within text is usually treated like a figure; therefore this new element should be part of the "figures" module and part of model.global.
Attribute Classes:
In addition to att.global it would be a member of att.typed and att.placement as this would allow basic classification (@type='rhythmic-pattern'; 'example'; 'movement'; 'full-piece') as well as indication of whether the music is located above/below/interspersed between the text being transcribed.
Content:
To allow a description of the music notation, the element should contain model.glossLike. Moreover, to give the possibility of pointing to external representations, the element should contain model.ptrLike.
In addition to model.glossLike this should have model.graphicLike in its content model to allow <graphic/> and especially <binaryObject/> for those who (for whatever weird reason) want to embed base64 encoded binary audio music representations or similar.
As a consequence of the TEI Music SIG Meeting at TEIMM 2010 on November 12, the proposal is update as follows:
Element name: music
Module and Classes: as above
Attribute Classes: as above, plus a type attribute with two recommended values: notation and sound
Contet: as above
@James, I really like the idea, especially for <binaryObject/> but I wonder what are the consequences of having <graphic/> there. Could that be used to embed an image of a score? Should <music> be preferred over <figure/> in that case? Is this desirable?
Yes, as we've discussed a proposed tei:music element is a figureLike element so should indeed have the ability to have a graphic in it. I feel that a tei:music/@type='notation' with a graphic element inside it would be a form of syntatic sugar for embedding a figure with a graphic pointing to a score. It would just be a more precise way of doing so and also allows for instead embedding MEI or something else, or indeed tei:binaryObject with a recording.
This makes it a much more general purpose element for denoting that some bit of the original here had music in some sense, which I think is a much more flexible approach. But I tend to fall into the if in doubt make it more general purpose and flexible camp rather than the if in doubt make it as tight as possible camp.
-james
I am on James' camp there. It sometimes takes ages to try to mend a too narrow model when people have started to adopt it.
Thanks everyone for your input on the feature request! Ok, I see your point in making the model more general. And if the FR 3113682 is accepted, then we also solve the problem with mime types that we were discussing on the Music SIG list. See: http://bit.ly/muSIG_mimetype
After some more discussion on the TEI-MUSIC-SIG list, we would like to suggest a tag name that brings us back to our original aim: marking the presence of music notation in text. Please consider this latest update:
Element name: notatedMusic
Member of: model.global
Attribute classes: att.typed; att.placemnt
Content: { (model.glossLike|model.ptrLike|binaryObject|graphic)* }
notatedMusic has already been added.