Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xsl] xslt2: Retrieving a directory's non-XML file names

From: "Michael Kay" <mike@------------>
To:
Date: 10/1/2008 5:36:00 PM
> An idea was occurring in my mind since quite some time. Can 
> we standardise the namespaces of extension mechanisms (at 
> least for Java) in XSLT (perhaps in versions after XSLT 2.0) 
> ? I guess it won't be much effort for different products to 
> comply, and would bring standardization in this area also.
> 
> Would be great if you could consider this proposal in the XSL WG.

The XSL WG attempted to standardize bindings to Java extension functions in
the abortive XSLT 1.1 proposal. The work was abandoned but you can still
find the working draft if you search for it.

There was very heated debate on the proposal at the time, on this list and
elsewhere. A sizeable section of the community took the view that it was not
the job of the XSL WG to standardize language bindings for Java or any other
flavour-of-the-day language, and the WG responded to this concern.

It would be nice if this could be taken up elsewhere, for example in the
Java Community Process, but at the moment I think that is unlikely to
happen. If it does, then judging from the speed of XQJ development, it will
take years to deliver anything.

Michael Kay
http://www.saxonica.com/


transparent
Print
Mail
Like It
Disclaimer
.

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 www.altova.com/list/index.html. 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.

.
.

transparent

transparent