xsl-list
[Top] [All Lists]

RE: killing xslt

2004-05-13 07:00:58
I believe it was last November that Michael Kay posted to the list
concerns regarding whether or not MS would be supporting XSLT 2.0 and as
such a call out to anybody who might be willing to support a port of
Saxon over to .NET.  I considered donating time to the effort but later
realized my workload was to great and as such wouldn't be able to give
the project a meaningful chunk of time to do something with.  What ever
happened to this thread?  Has a secret society of XSLT devout taken on
the task in silence or did the post simply not garner enough attention
at the time to get anything off the ground?

Is it time to resurrect the thread, using Microsoft's own Java to C#
conversion tool (in beta of version 3 now so its obviously being used)
to give us a head start on the port?  Or are there any other XSLT2.NET
projects out there that have come about because of similar concerns that
caused Michael to make that post 6 months ago?

There is too much opportunity here for me to believe that someone hasn't
already begun either a port of Saxon or a brand new engine that will
support the 2.0 standard on .NET.  And if there's not, well then the
opportunity is once again ours to take on Michael's original challenge.
It seems to me the same group that developed EXSLT for .NET would have a
lot to contribute to something like this and that same working
infrastructure might be the perfect pre-existing organization to look to
facilitate the efforts in that they have already gone through the
growing pains of developing an open source XSLT processor project for
.NET.  Are any of you guys currently reading this thread and have input
to say regarding this matter?

Thoughts?

<M:D/>

-----Original Message-----
From: bry(_at_)itnisk(_dot_)com [mailto:bry(_at_)itnisk(_dot_)com]
Sent: Thursday, May 13, 2004 8:11 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: [xsl] killing xslt

note the following:
http://weblogs.asp.net/mfussell/archive/2004/
05/13/130969.aspx

Well this is sort of weird for me, I
remember when the xslt 2.0 recs were first
coming out, and all the arguments we had,
one of things I considered then, and I think
I argued it, was that the hideous marriage
with xsdl was basically driven by microsoft,
natural enough given their wholesale
acceptance of xsdl.

Given that there was some concern that some
of the smaller xslt processors would not be
able or would be unwilling to make
improvements to support xsdl I felt that
this urging on of the schema integration was
definitely a drawback, given that probably
there would only be a couple of processors
willing to support it. That in essence xsdl
support was killing off xslt.

Now I'm not so sure about accidentally.

IIRC MS announced some time back that there
would be no further updates to MSXML, other
than I suppose service packs and bug fixes.
So MSXML will not be supporting XSLT 2.0,
and .NET will not be supporting XSLT 2.0,
and thanks to the largeness of XSLT 2.0, the
largeness of XSDL, and of course debates
about the meaning of large areas of the
schema spec how many processors for the next
version of the language can be counted on?
And what is the likelihood of those
processors being cross-platform compatible?








--+------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--+--



<Prev in Thread] Current Thread [Next in Thread>