From: Michael Kay <michael.kay@nt...> - 2002-03-29 20:52:50
The XSLT 1.1 working draft (http://www.w3.org/TR/xslt11) attempted to define
Unfortunately it proved controversial, and has effectively been withdrawn.
However, most of the Java implementations provide something pretty close to
> -----Original Message-----
> From: saxon-help-admin@...
> [mailto:saxon-help-admin@...]On Behalf Of
> Mark Diggory
> Sent: 29 March 2002 17:06
> To: saxon-help@...
> Subject: [saxon] Ideas about extensibility
> I've be digging into the examples about extensibility in Saxon. I'm
> curious what's up with the XSLT Community in terms of a standard
> "interface" for extensions that all XSL Transform
> implementations could
> support? Is there any work being done on this at this time?
> The benefits of such an interface would be immense. Just look at JSP
> Custom Taglibs as an example of extensibility done right. Now that
> there's a "standard interface" for extending JSP with Custom Taglibs,
> allot of tools have been developed that auto-generate
> "template classes"
> (see Forte by Sun as an example).
> I imagine the day when I can hop into my IDE and generate "shells" of
> code for element and function extensions and then customize
> them for my
> -Mark Diggory
> saxon-help mailing list