[tei-council] notated music

James Cummings James.Cummings at oucs.ox.ac.uk
Mon Jul 4 11:52:46 EDT 2011

On 04/07/11 16:34, Martin Holmes wrote:
> I don't want to block this, but I do think we might be doing several
> things at once here. There seem to be three distinct issues:
> 1. The need for an<externalObject>  (or whatever) which is specifically
> designated as a transclusion element.
> 2. The need for a container element whose content elements are deemed to
> be not choices exactly but somehow parallel renderings in different
> formats of the same content (an image of notated music, an XML rendering
> of it, an MP3 file of the music). This contrasts with<choice>, which
> apparently assumes that one of its content elements will be chosen in
> any given context.
> 3. The need for<notatedMusic>, which is semantic sugar for
> <aboveContainer type="notatedMusic">.

I agree with this, except for the assumption about choice which 
is tangential here. (For the record, I feel choice is probably 
misnamed because in most processing of it these days we do *not* 
make the choice... we might privilege one over the other, but in 
most renderings I've seen both are available in some way (often 
able to be toggled or present in a tooltip etc.).  This is 
exactly what I usually do with choice.  But none of this matters 
for this discussion.

> If my understanding above is correct, then I think it would be better to
> make three separate feature requests, and deal with #2 before #3. Or am
> I missing something?

Nope, that sounds correct to me.  My only worry is that #2 is 
likely to cause much discussion whereas in general #3 is fairly 


Dr James Cummings, InfoDev,
Computing Services, University of Oxford

More information about the tei-council mailing list