Hi Piotr,

I am not so sure that this is what I meant …. 

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.

Of course, an element can have many attributes that are relevant for formatting, but if required, the <tagUsage> with a certain @gi could be repeated.



On 6 Oct 2014 at 12:55:04, Piotr Bański ([log in to unmask]) wrote:

Hi Jens,

I'm wondering if the same could not be achieved by fixing the
appropriate styling data in the ODD, by modifying the declaration of
"p". Unless I misunderstand, what you are suggesting sounds to me
exactly like doubling the functionality of the ODD mechanisms.

Best regards,

(registered for the ODD workshop, to rehash and to learn more...)

On 06/10/14 12:06, Jens Østergaard Petersen wrote:
> Formatting is often tied up with the values of attributes, but it is not
> possible to make a tagging declaration which refers to attributes. Would
> it make sense to expand the number of attributes on <tagUsage> to
> something in the manner of
> <tagUsage gi="p" att="type" att-value="intro"
> render="#p-intro">introductory paragraph</tagUsage>
> One could then create a <rendition> which would operate not just on
> element level, but on element plus attribute level – one might even wish
> to allow leaving out the element (now mandatory) and style all elements
> with certain attribute values in a certain way.
> The idea is to make it possible for a project to style individual
> documents (or a document corpus) in a TEI application without having to
> fiddle (too much) with the code.
> Jens