& XSLT NOTE: Am resending what follows as my first attempt failed due to using  
the wrong From: email address.  My apologies if somehow the first message  
sneaks through and you get this twice!

On Tue, 19 Jun 2007 13:41:57 -0600, Dimitre Novatchev  
<dnovatchev@[...].com>  wrote:

I think that specifying such an extension falls exactly into the
subject area of EXSLT, unfortunately until no one has proposed a
specification.

I agree wholeheartedly that this is exactly the thing that EXSLT should  
champion.

@EXSLT List Members: The body of Dimitre's original message to XSL-List  
follows.  This conversation should probably be moved off of XSL-List, but  
am leaving XSL-List as a recipient to encourage those who are not already  
subscribed, but would like to join the conversation, to visit  
http://lists.fourthought.com/mailman/listinfo/exslt and then do just that.

The context is provided first,

---
On 6/19/07, M. David Peterson <m.david@[...].com>  wrote:
On Tue, 19 Jun 2007 06:25:40 -0600, Dimitre Novatchev
<dnovatchev@[...].com>  wrote:

Once we have an implementation of a library of XSLT functions, one
would simply use the compiled version of FXSL or whatever else.

Can you expand what you mean by this?  Are you referring to a stand-alone
FXSL processor/library (that's how I immediately interpreted this, so
thought it best to clarify)

Sure. The compiling XSLT processors that I am aware of compile a
primary stylesheet with all included and imported stylesheets into a
single executable module. This module is then used to perform a
definite, specific transformation on any xml source document we want
to apply the  transformation to.

I have been discussing (in this list, I think) the high value of being
able to compile stylesheets that are not primary (such as containing
only xsl functions). Then there should be a standard mechanism for any
primary stylesheet to (link to) use the so compiled library of xsl
functions.

I think XQuery has such a facility -- the module.

Dr. Kay did express his opinion that implementing this for XSLT (just
following what we have for XQuery) shouldn't be difficult.

Certainly, an extension (element or attribute) will be necessary to
declare local externals to export and to needed externals to import
 from other modules.

I think that specifying such an extension falls exactly into the
subject area of EXSLT, unfortunately until no one has proposed a
specification.

--
Cheers,
Dimitre Novatchev
---

--
/M:D

M. David Peterson
http://mdavid.name | http://www.oreillynet.com/pub/au/2354 |  
http://dev.aol.com/blog/3155
_______________________________________________
exslt mailing list
list@[...].org
http://www.exslt.org/list