Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


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

From: "Mukul Gandhi" <gandhi.mukul@--------->
To:
Date: 10/1/2008 6:12:00 PM
Hi Mike,

On Wed, Oct 1, 2008 at 11:05 PM, Michael Kay <mike@xxxxxxxxxxxx> wrote:
> 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.

I could give an example of a W3C language; the very popular DOM. W3C
has also defined HTML bindings for DOM.

Can't we do similarly for Java bindings for XSLT? If there is
sufficient market demand, we could think of other languages too ...

Your idea of taking it up as a JCP process doesn't satisfy me much. I
think, JCP is more to do with Java APIs development.

This problem is mostly concerned with XSLT, so I would think, this
should be taken up under W3C guidance.

I also think, that developing Java bindings for XSLT will not be a
length specification (it would be 2-3 pages I guess). I think this
does adds value to the XSLT community ...

-- 
Regards,
Mukul Gandhi


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