[tei-council] rendition in ODD

Sat Jun 23 08:42:35 EDT 2007

<div class="mail">
<address class="headers">
<span id="from">
<dfn>From</dfn>: Laurent Romary <laurent.romary_at_loria.fr>
</span><br />
<span id="date"><dfn>Date</dfn>: Sat, 23 Jun 2007 14:42:35 +0200</span><br />
</address>

I would also agree with this point. Anyhow, we should probably keep 
 
on one of the post 1.0 face to face council meeting a discussion on 
 
the role of ODD and its evolution.

Le 23 juin 07 à 13:52, Lou Burnard a écrit :
<br />

> I don't doubt that this is an interesting and possible evolution 
 
> for the ODD specification, but I would rather not make this 
 
> development right now without thinking it through properly. My 
 
> point is just that it is not currently in scope for what we can 
 
> hope to achieve for TEI P5 release 1.0 and that we already have an 
 
> adequate means of solving the specific problem in hand, viz using 
 
> rendition in the header.
 
>
 
>
 
> Laurent Romary wrote:
 
>> I have just understood what Sebastian meant there and I think he 
 
>> is going in the right direction, i.e. ODD specifications, with 
 
>> their capacities of representing hierarchies of schema, could be 
 
>> used to express constraints ranging from general TEI 
 
>> specifications, down to project specific constraints and even, at 
 
>> times, document specific ones. The trade-off here is to view 
 
>> rendering constraints either as something you would like to put +in 
 
>> + the document (in the header) or outside, in particular when you 
 
>> would want to share the constraints among various documents 
 
>> (without having all of them gathered in a TEI corpus).
 
>> Bref, I like the idea...
 
>> Laurent
 
>>
 
>> Le 23 juin 07 à 12:11, Sebastian Rahtz a écrit :
 
>>
 
>>> Lou Burnard wrote:
 
>>>> but rendition, even default rendition, is not a property of the 
 
>>>> element itself, but of the document in which it appears. so it 
 
>>>> should not be polluting the *spec, but tidily wrapped up in the 
 
>>>> header for the document in question, where it belongs,
 
>>> so 50,000 documents each of which say that <term> should be in 
 
>>> italic have to have 50,000 <rendition> elements?
 
>>> gimme break.
 
>>>
 
>>> when I make an ODD, I say that _in this project_ &#64;rend on <hi> 
 
>>> will have values
 
>>> "bold", "underline" and "subscript", because I have observed this 
 
>>> in my documents.
 
>>> I also want to record how to render those in CSS using font-style 
 
>>> or whatever.
 
>>> what is more natural, and One Document Does it all-like, to store 
 
>>> these font-style
 
>>> things with the relevant <valItem>?
 
>>>
 
>>>
 
>>> --Sebastian Rahtz
 
>>> Information Manager, Oxford University Computing Services
 
>>> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
 
>>>
 
>>> _______________________________________________
 
>>> tei-council mailing list
 
>>> tei-council_at_lists&#46;village.Virginia.EDU
 
>>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
 
>>
 
>>
 
>
 
> _______________________________________________
 
> tei-council mailing list
 
> tei-council_at_lists&#46;village.Virginia.EDU
 
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council

_______________________________________________
<br />
tei-council mailing list
<br />
tei-council_at_lists&#46;<!--nospam-->village.Virginia.EDU
<br />
http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
<br />
<span id="received"><dfn>Received on</dfn> Sat Jun 23 2007 - 09:00:11 EDT</span>
</div>