[tei-council] <notatedMusic> changes required

[Martin Holmes]

Hi all,

I think this debate is interesting, and it could go on for a long time. 
But we didn't actually get anything useful from my little poll. So far 
we have (forgive me if I've misinterpreted you):

1. @type="transclude"      Martin M

2. @rend="transclude"      [possibly Sebastian]

3.          [nothing]      Raffaele, Laurent, Gaby, Martin H

Additional write-in option by Sebastian:

4. Rewrite the exx not to use ptr at all; use XInclude instead

Obviously uneasy but not giving explicit preferences:

Lou, James.

The rest of the council appear to be away, or have no interest or 
opinion. On that basis, I'm going to leave the <ptr> examples with no 
@type or @rend for the moment.

Cheers,
Martin

On 11-07-08 04:02 PM, Martin Mueller wrote:
> It's not just Sebastian who spends a lot of time rendering code. It's
> everybody in the TEI, and everybody is or ought to be grateful to
> Sebastian for making their own work a lot easier. It's the fate of TEI to
> live in a world where it always needs to be translated into something
> else, mostly html. So to the extent that conventions are variable and
> involve trade-offs between different priorities, I would put a high value
> on ease of subsequent processing and suggest that in thinking about
> whether to do X this way or that way it will be a good think to pay
> attention to whether the processors down the line will breathe sighs of
> relief or mutter under their breath.
>
> On 7/8/11 4:45 PM, "Sebastian Rahtz"<sebastian.rahtz at oucs.ox.ac.uk>  wrote:
>
>>
>> On 8 Jul 2011, at 21:02, Martin Holmes wrote:
>>
>>> 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.
>>
>> Yes indeed, I fully admit admit my bias. But to turn that around,
>> if I can't interpret a file in a standardized way, its not interoperable,
>> so whats the point of it?
>>
>> If we have no expectation of how to process<ptr>,
>> then  how do we distinguish between the case of a musical
>> notation present in the source text (in a format which we can't
>> put in TEI, and so needs ref to an external file), and the case of
>> a hyperlink to a musical notation resource in the source file?
>> if you say, "well, you have to look at the container,<notatedMusic>,
>> which
>> cannot contain hyperlinks, so courses in the former",
>> then I will reluctantly accept it, but curse because
>> you've made my processing more complex.
>>
>> --
>> 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
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> tei-council mailing list
>> tei-council at lists.village.Virginia.EDU
>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>
>> PLEASE NOTE: postings to this list are publicly archived
>
>
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>
> PLEASE NOTE: postings to this list are publicly archived