XSLT v. XQuery

Well I hope Microsoft will reconsider it support for XSLT and support XSLT 2.0

(For one, it will make it a lot easier to convert WordML to a real, standards-compliant and semantically meaningful XHTML output...!)

What's the difference between XQuery and LINQ?

Good to see you taking interest in this. Just in case you were unaware, see http://www.xsltblog.com/archives/2006/02/saxonsaxonnet_v.html which is the announcement in regards to the transfer of Saxon.NET to Saxonica, in which Dr. Kay has officially taken on the continued development and support for this project, which in and of itself is a pretty cool thing, and a HUGE boost to the overall acceptance of XSLT 2.0 and XQuery for .NET developers.

You can access the overview of Saxon on .NET (the new product name) starting here > http://www.saxonica.com/documentation/changes/intro87/dotnet87.html and a quick and dirty sample ASP.NET intro > http://www.oreillynet.com/xml/blog/2006/04/update_hello_saxon_on_net_an_a.html < (link to the original sample is contained on this same page)

As mentioned in the above link, as soon as the new LiveClipboard spec/samples release I will be extending this demo into some cool areas that I hope will start to extend the ideas of how XSLT 2.0 can be used in a centralized web application message transformation control center, in which mapping the content of one XML package to any given (and mappable) format and back again becomes as simple as passing in the XML as either a .NET Stream or an implemetation of XmlDocument, along with setting the desired output format via a parameter.

Hope this info helps!