On 6 Oct 2014, at 15:02, Jens Østergaard Petersen <[log in to unmask]> wrote:
> Say a TEI document is processed by some terribly intricate XQuery or XSLT code. Most often, formatting instructions are hardcoded in the XQuery or XSLT code, but with TEI as it is now, every time the processor comes upon a <p> element, it could look up the desired <rendition> in <tagUsage> in the document's header and (assuming this uses CSS) inject the styling rule into the XQuery or XSLT code (perhaps overruling some default styling rules contained there) and render the <p> accordingly. If the XQuery or XSLT code is set up to take advantage of this, this would allow the TEI encoder to declaratively control how the document is to be rendered, without having to dig into the XQuery or XSLT code. This is the advantage of the present TEI setup that I wish to leverage. The problem I see is attributes: these often have consequences for formatting, but cannot be referenced in <tagUsage>, so my suggestion was to make this possible.
You may be interested in the TEI Simple (https://github.com/TEIC/TEI-Simple) project which is now underway. One of our outputs will be an ODD notation which lets you
write the default styling rules, and say whether or not the @rendition or @rend should be looked up and acted upon. There’ll be a presentation about this in a
few weeks at the TEI Members meeting
Director (Research) of Academic IT
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
Não sou nada.
Nunca serei nada.
Não posso querer ser nada.
À parte isso, tenho em mim todos os sonhos do mundo.