I remember Sebastian and I talking about this when <rendition> was first
introduced and the problem I had was that it seems more that <rendition>
elements would store things akin to an <xsl:template>. The problem
comes with stylesheets that are not simple template mappings but have a
more programmatic nature. It seemed wrong to me to embed an entire
<xsl:stylesheet> into a single <rendition> element, and I think that
breaking it up in a template - rendition equivalence also doesn't work.
In a similar idea of embedding related documents into your TEI document,
I once made a (non-conformant) TEI ODD whose schema allowed one to embed
an entire ODD inside <encodingDesc>. The idea being that one could be
able to regenerate the schema from the document instance. I am not
actually suggesting people do that, it was just a bit of fun. However,
it is one option, change <encodingDesc> to also allow an
<xsl:stylesheet> to be embedded inside it. Again probably not the best
idea, but certainly a possibility.
Dot Porter wrote:
> I've only thought of <rendition> in terms of the display of individual
> elements (as the examples on the index page) - but yes, if I were
> going to place an XSLT stylesheet in my file, this is where I'd put
> it. From the description it sounds like it could also contain a
> pointer to an external file, which is what Torsten seems to be asking
> for in his original request. Nifty!
> On Tue, Jul 21, 2009 at 10:45 AM, Sebastian
> Rahtz<[log in to unmask]> wrote:
>> This is what we invented <rendition> for, surely?
>> <rendition> allows you to express a rule about formatting
>> In a variety of languages (CSS, FO, etc). There are few (no?) examples
>> Of non-CSS use, I think, but its a container waiting for people to
>> Explore the use of.
>> Sebastian rahtz
Dr James Cummings, Research Technologies Service, University of Oxford
James dot Cummings at oucs dot ox dot ac dot uk