RE: [xsl] killing xslt

[Pieter Reint Siegers Kort <pieter.siegers@xxxxxxxxxxx>]

Well, fully implemented or not, the idea of this project is to see if the
switch to C# using MS own Java to C# converter utility could be a feasible
one.

One step I didn't include was the next one: implement more XSLT 2.0, Xpath
2.0, and XQuery 1.0 support as time goes by. But that's afterwards, if you
know what I mean... first look if it's something worth the time and trouble.

I am still open to start the project; I'll at least try the utility and see
what quality of C# comes out, and what kind of problems are raised by the
utility.

If somebody else feels kind of in for this project, pls. let me know
(mail@xxxxxxxxxxxx).

<prs/>
http://www.pietsieg.com
http://www.pietsieg.com/dotnetnuke

Contributor to ASPToday.com: http://www.asptoday.com/Authors.aspx?ID=101
Co-author of "Professional ASP.NET XML With C#", July 2002 Wrox Press (now
Wiley's)

My own XQuery resources:
http://www.pietsieg.com/sections/XQuery/ArtXQueryBeg.aspx
http://www.topxml.com/xquery/default.asp


-----Original Message-----
From: Bob Foster [mailto:bob@xxxxxxxxxx] 
Sent: Friday, May 14, 2004 11:40 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] killing xslt

Pieter Reint Siegers Kort wrote:
> Like David, I would be interested in setting up an open source project 
> but would prefer using C#, VS.NET 2003, to do the port from Saxon 
> 7.9.1. Not on my own, of course... :-)

That does sound interesting and eminently doable.

However, Saxon 7.9.1 is not XSLT 2.0. Specifically, it does not have
validation and the strong type assignment that results from validation. 
To quote the website: "A schema-aware version of the product is planned: 
this will be a commercial product available from Saxonica Limited."

I don't know exactly how this would affect the ability to deliver a fully
functional XSLT 2.0 for .NET based on Saxon.

Bob Foster
http://xmlbuddy.com/