RE: [xsl] XQuery 1.0 and XPath 2.0 Functions and Operators Version 1.0

Subject: RE: [xsl] XQuery 1.0 and XPath 2.0 Functions and Operators Version 1.0
From: Joerg Pietschmann <joerg.pietschmann@xxxxxx>
Date: Thu, 06 Sep 2001 12:12:12 +0200
"Chris Bayes" <chris@xxxxxxxxxxx> wrote
> Well it is a good idea to keep it small I'd like to see xsl become all
> pervasive even to handheld devices as well as to mainframe database
> apps.
> As long as the extension mechanism is well defined and standard across
> all xslt 2.0 implementations then things like trig functions can be
> added as needed.

I'd rather have a small core functionality and some well defined,
standardized libraries which implements additional functionality
and may be unavailable on certain platforms/implementations.
Some possible libraries/packages:
 extended math/trig
 user information database access
 output control
 file system access (file existence, modification date...)
 extended node set manipulation (sort, uniq, symmetric difference...)
 localised string manipulation (upcase...)
 unicode character transformations ("uncompose", making characters from
 font property access (fit SVG rectangles around a string)
 image property access (format/encoding, width, hight, color depth...)
Namespaces woul prevent name clashes, as usual.
It would be interesting whether standardized *XSL* libraries would
not only include XPath extension functions but also built-in
variables (aka constants) and predefined templates. Stuff the processor
knows about could be more efficiently implemented/preoptimized.

For example:
<xsl:stylesheet xmlns:xsl="";
  <xsl:template match="/">
   <xsl:if test="not(xslposix:file-accessible('lock'))">
     <xsl:call-template name="xslposix:mkdir">
       <xsl:param name="name" select="concat('stuff',xsltrig:sin(0.1 * $PI)"/>

Oh well, i've probably gone much too far...


 XSL-List info and archive:

Current Thread