Lou Burnard wrote:
>some values. This means that an implementor can be pretty sure what to
>do with (say) <list type="ordered"> or <list type="gloss">, but may
>well also be confronted by a <list type="frabjous"> or <list
>type="potzbrje"> which the TEI Lite schema will happily accept. This
>shocking liberalism applies even more to the notorious REND attribute.
Speaking as an implementor, this is spot on. The totally unconstrained
use of "type" and "rend" is a serious problem. If you meet "rend",
you can be fairly sure you are supposed to do something, but
does "<div3 type="section"> mean that this _overrides_ the
assumption that a 3rd level division is a subsubsection (in some parlance),
or is it a remark intended for some analytical purpose?
How about the glorious
if you want a challenge for CSS-type rendering :-}
>I'm curious as to what you mean by "direct rendering": from context it
>appears you mean "using CSS to attach formatting properties to specific
>XML constructs". There are quite a few TEI notions for which that won't
>really hack it -- out of context <note>s is one.
>TEI has no table model to speak of -- it says tables are made of rows,
>which are made of cells. And that's about it!
>This is again something that implementors have difficulty with when it
>comes to rendering TEI tables.
the main problem is lack of guidance about column widths and cell
I don't believe that anyone could write a satisfactory algorithm
for guessing column widths, as the decision may be biased by the
relative importance of columns, which you cannot deduce from the markup.
Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
OSS Watch: JISC Open Source Advisory Service