Re: Template repository (Was: Re: [xsl] Re: namespace values)

[Jeni Tennison <mail at jenitennison dot com>]

Hi Jim,

>> It'll be fairly simple to change the exsl:function definitions into
>> similar templates to do roughly the same thing, so I'll do that.
>> One thing, though - should I include within them shortcuts using
>> implementation-specific functions. For example:
>> 
>>   <xsl:template name="math:min">
>>      <xsl:param name="node-set" select="/.." />
>>      <xsl:choose>
>>         <xsl:when test="function-available('saxon:min')">
>>            <xsl:value-of select="saxon:min($node-set)" />
>>         </xsl:when>
>>         ...
>>         <xsl:otherwise>
>>            <!-- XSLT recursive template -->
>>         </xsl:otherwise>
>>      </xsl:choose>
>>   </xsl:template>
>> 
> i like this idea, but maybe we would like to eventually 'extract' a
> library for each specific xsl parser, so we should think about a
> transform, to do this, on the above example template or maybe
> seperating versions using modes and xsl:includes; prob too
> cumbersome that.

The point, though, would be to supply utility stylesheets that would
work under any processor, and be portable between them, to encourage
people to write portable stylesheets rather than processor-specific
ones.

>> As I've been thinking about the function repository, I've been
>> thinking about an XML structure to hold the pertinent information
>> about the functions; we need something similar for a template
>> repository as well.  If anyone would like to work on designing that
>> XML format, please stick up your hand.  It will make submissions a lot
>> easier if we have it.
>
> will give a shot

Great :)

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list