RE: [xsl] Group and compare data

Subject: RE: [xsl] Group and compare data
From: Pieter Reint Siegers Kort <pieter.siegers@xxxxxxxxxxx>
Date: Wed, 6 Oct 2004 18:26:22 -0500
Hi Thomas,

Yes you could very well use the Saxon.NET.dll, but keep in mind that it is
still a very early beta release, and is still subject to extensive testing.
But if you want to, go ahead, and let me know your findings. 

XSLT 2.0 isn't going to be supported by MS. They think XQuery can do the job
for all applications, but I think that XSLT and XQuery are merely
complementing technologies. Apart from that, if you have been using XSLT
1.0, it is much more logical and easy to upgrade to 2.0. 

I personally come from a database background, and would be more than happy
to use XQuery in many applications that I have written. I plan to do so in
the near future. 

On the other hand, I have used XSLT 1.0 for a while now, and I've become
quite a fan, using it more and more every day in my normal programming work
on .NET.

So the fact that MS isn't going to support XSLT 2.0 / XPath 2.0 was kind of
a dumper for me - I felt the same as a few years ago when they shut down
VB's Web Classes - I had written a couple of articles about it on
ASPToday.com and had started to use it in my applications - it was just
cool. Then it was changed for something even more cool according to MS. Not
for me though - at that time, at least.

All said, Java with Saxon runs smoothly on Windows. If you want to bridge
Java to MS products, you can do it. For example, it should be fairly easy to
let a C# application call a Java process, let it run, and get back the
results asynchronously when it's ready. This is just an example of course.
Take care of the way that Java returns the results though.

I'll leave the subject here, because I see I'm quite OT... :-))

Cheers,
<prs/>


-----Original Message-----
From: Verakso [mailto:verakso@xxxxxxxxx] 
Sent: Wednesday, October 06, 2004 4:07 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] Group and compare data

> 2.0 solution:

Hmm bugger.  I am running a strictly MS solution here, but perhaps I should
look into the saxon.net port

> In XSLT 1.0, you need to write a recursive template. It's tedious, so 
> I'll leave it to others.

That I did find out, and it went bad for me.

I'll guess it must have been up on this list a thousand times before, but
does anyone have a good clue on wheter MS is going to support XSLT2, and
what the future for eg. MSXML is. I found that there was a
v5 installed along with my new office, but I does not expect it to support
XSLT2.

/Thomas

Current Thread