RE: [xsl] killing xslt

["M. David Peterson" <m.david@xxxxxxxxxx>]

My apologies for being slow to respond back to your call out Pieter.  I
just returned from Denver a day later than planned and am now catching
up on email.

I too have offered both server and development support for this project
on a thread separate from this.  I had intended to spend this weekend
using the conversion tool to transform the latest 7.9.x Saxon source.
But it seems silly to not first get all interested together, synched up,
and a plan put into place.  Would also like to see what type of feedback
we can get from Michael Kay regarding his thoughts about the effort that
would be needed to make the port as well as any problems or issues that
he feels we may encounter during the process.  Going into the project
armed with as much information as possible would obviously give us an
edge during the conversion.

I will contact you using the email you published on this thread.  But I
will use thread to encourage further the need for support for a project
like this.  Being away from my computer for a bit and being able to put
quite a bit of thought into the occurrences of the last few days has led
me to believe that the most important thing that needs to be done is to
look at every possible solution that we as developers have to solve our
development problems.  As such it is going to be just as important for
us to try and look at the code necessary to solve various common
transformations AS WELL AS querys to access a particular subset of data
from both XML and SQL sources.  It seems that if we put the time into
trying out every proposed combination of solutions we will be much
better informed to make a final position on whether or not XSLT 2.0
support on .NET is something that is as important as we believe it is.
Having the ability to transform XSLT 2.0 code on .NET is obviously very
crucial to developing the data to make an accurate and well informed
decision either way.

I have quite a few URL's that I have registered over the years and a
month or two ago I registered the .COM.NET.ORG for X2X2X which I was
using to represent XSLT 2.0 XPath 2.0 and XQuery and have plans to use
the .COM version of the domain to act as the web front end version of a
book I have planned that covers all three of these languages and
solutions that use the power given to us by all 3 to solve the
development scenarios that we as developers are faced with on a
day-to-day basis.  The .ORG version as of yet has no plans for use and
as such may act as a good interface to an the organization of developers
of whom plan to use these technologies in there development and are
willing help with the effort to build a common tool bag for all of us to
benefit from.

Any one else out there willing to help with the various aspects of this
proposed project?  No need for multiple people fielding responses so Ill
just republish the Pieter's email and allow him to continue with
coordinating this effort.

mail@xxxxxxxxxxxx

Other than making a final determination as to what domain name seems
appropriate (would be difficult to use an alias to communicate that
hasn't been created :) it seems that from here on out we should probably
take the communication about this project through a separate alias as
this thread has definitely gone past the intended purpose of this list
to support actual development using XSLT.  Once we have determined what
domain name seems appropriate then we can post it back to the list to
let people know where to go to offer support, communicate about the
project, etc....

Comments regarding the domain name to use?

Again Pieter, I will contact you via your posted email to discuss the
next step in the proposed effort.

Best regards,

<M:D/>

> -----Original Message-----
> From: Pieter Reint Siegers Kort [mailto:pieter.siegers@xxxxxxxxxxx]
> Sent: Saturday, May 15, 2004 12:40 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE: [xsl] killing xslt
> 
> 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/