[tei-council] <notatedMusic> changes required

[Martin Holmes]

Hi Sebastian,

Your explanation makes perfect sense, but:

I think if you spend a lot of your time writing rendering code -- i.e. 
turning TEI code into other formats which will be consumed by readers -- 
then it's tempting to see all TEI elements has having or needing some 
kind of intrinsic expected rendering behaviour; when you're writing the 
TEI stylesheets, you're essentially codifying those expectations. But I 
think that's where that information belongs -- in the stylesheets, not 
in the XML itself. TEI is supposed to be a long-term archive format, 
among other things; if it's used to mark up an existing document, it's 
describing it, not prescribing rules for processing it. Twenty years 
from now, the notions of linking or transclusion may have rather 
different meanings.

To me, this:

<graphic url="foo.jpg"/>

means "There was something in the original text which is represented in 
graphical form in a file. Here's where you can find that file if you 
need it."

It definitely doesn't say "Here's a graphics file, which you are 
expected to incorporate into any output you may be creating from this 
file."

But I suspect this is a philosophical difference regarding what we mean 
when we mark up a text.

Cheers,
Martin

On 11-07-08 10:34 AM, Sebastian Rahtz wrote:
> Let me try my pitch again.
>
> It is agreed that an element which has an attribute of datatype data.pointer points
> to some resource on the internet.  It does not _per se_ dictate what we should
> do with that pointer if we render the document.
>
> However, I would say that the behaviour is very strongly indicated by the
> element which has that attribute. so
>
>        <graphic url="foo.jpg"/>
> and
>           <ptr target="foo.jpg"/>
> and
> <writing source="foo.jpg"/>
>
> all point to the same resource (with no indication of what you might find there, or why
> you going there), but the conventional (tho not mandated) behaviour
> is determined by "graphic", "ptr" or "writing".
>
> So to my mind
>
>     <notatedMusic>
>       <graphic url="foo.svg"/>
>          <ptr target="http://example.com/foo"/>
>   </notatedMusic>
>
> is a conceivable formulation, and means that if you cannot pull in the graphic,
> you should just put it a link which the reader can follow at leisure. If I saw
>
>     <notatedMusic>
>       <ptr target="foo.svg"/>
>       <ptr target="http://example.com/foo"/>
>   </notatedMusic>
>
> it really does not mean the same thing to me.
> --
> Sebastian Rahtz
> Head of Information and Support Group, Oxford University Computing Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>
> Sólo le pido a Dios
> que el futuro no me sea indiferente
>
>
>
>
>
>
> .
>

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)