Re: killing xslt

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?