Re: Future of EXSLT

Hi all,

There are certain functions that would be useful extensions to XQuery that
are not needed in XSLT.  Hopefully we could include those in the same
"EXSLT" effort.

Some of them are XSLT functions but not XPath functions, like format-date,
format-number, generate-id.  These could easily be specified using the same
signatures as in the XSLT 2.0 rec.

Others are already handled by XSLT 2.0 instructions that have no equivalent
in XQuery. For example, it would be useful to have something to get the
matching and non-matching parts of a string, like saxon:analyze-string[1] or
functx:get-matches-and-non-matches[2].

Thanks,
Priscilla


[1]
http://saxonica.com/documentation/extensions/functions/analyze-string.html
[2]
http://www.xqueryfunctions.com/xq/functx_get-matches-and-non-matches.html 

> -----Original Message-----
> From: [email protected] [mailto:exslt-
> [email protected]] On Behalf Of Florent Georges
> Sent: Thursday, December 18, 2008 1:08 PM
> To: Robert Koberg; EXSLT Mailing List
> Subject: Re: [exslt] Future of EXSLT
> 
> Robert Koberg wrote:
> 
> > I realize this is eXSLT, but wasn't this going to be more about
> > extensions for XPath? That is, something that can be used by both
> > XSLT and XQuery.
> 
>   There are several ways of defining extensions for XSLT.  I guess most
> of the extensions for XSLT 2.0 in EXSLT will be extension functions.
> So they will be applicable to any XPath host languages, like XSLT and
> XQuery, but also any XPath library for, say, Java or .NET.
> 
>   Regards,
> 
> --
> Florent Georges
> http://www.fgeorges.org/
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> exslt mailing list
> [email protected]
> http://www.exslt.org/list