Altova Mailing List Archives

Re: [xsl] XSLT 1.1 comments - the chocolate hobnob challenge

From: David Carlisle <davidc@--------->
Date: 2/15/2001 7:37:00 AM
> What really worries me is that an extended period during which the spec
> privileges non-platform-portable extension functions over XSLT extension
> functions will do irreversible damage in terms of fragmenting the
> codebase and encouraging people to drop the idea of platform-independent
> portability as a realistic goal for XML technologies.

I'd very much like to see a mechism for defining functions in XSLT. Not
only to "save keystrokes" on the syntax of parameters to named templates
(although that in itself would be fairly good reason) but rather because
I can call functions inside deeply nested XPath expressions in ways that
are really difficult using named templates and variables. So it seems to
be extra functionality not just fewer keystrokes.

But I'm not sure how much adding that would remove the need for
external extension functions of the types currently used.
If you use an external function to use a regexp handler
or language aware date library, then you are unlikely to want to code
that functionality in XSLT eiher as a function or a named template. 

So I don't see that non xsl functions are "privileged". They are a
necessary evil.

I don't suppose I get the biscuit for this reply (Are you going to
provide a pint of Old Peculier to wash them down?)


This message has been checked for all known viruses by Star Internet delivered
through the MessageLabs Virus Control Centre. For further information visit

 XSL-List info and archive:


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.