XSLT 2.0

re: XSLT 2.0

tzagotta — Tue, 30 Jan 2007 03:07:59 GMT

How does the work on XSLT 2.0 affect the probability of getting an XQuery implementation into the .NET Framework? I am kind of getting the impression that XQuery is not going to happen?

re: XSLT 2.0

Mike Champion — Tue, 30 Jan 2007 03:32:04 GMT

We will make a separate post about XQuery -- the story is a bit more complicated, and we didn't want to delay confirming that we are actively working on XSLT2 but that it will not appear in "Orcas."

But the bottom line is that the probability depends partly on how much demand we see for querying *standalone* XML documents with an XQuery implementation separate from the one in SQL Server. By all means let us know your needs via the contact form.

re: XSLT 2.0

Jim Burger — Tue, 30 Jan 2007 03:43:40 GMT

That is fantastic news, thankyou very much for pushing this through. I look forward to checking it out.

XSLT 2.0 in Microsoft.NET?

Wictor Wilen — Tue, 30 Jan 2007 10:41:42 GMT

As you probably already have read by now is that the XSLT 2.0 and XPath 2.0 are now W3C Recommendations. XSLT 2.0 is a really nice step forward in the XML transformation technology, a technique that w...

re: XSLT 2.0

XSLT & XML in .net 2.0+ — Tue, 30 Jan 2007 17:50:59 GMT

The XMLDocument .net class really worked well for basic XML file processing. I hope to see better XML tools in Visual Studio (e.g., a something similar to a query designer for XSLT XPath queries).

re: XSLT 2.0

xmlhacker — Wed, 31 Jan 2007 04:37:11 GMT

You are all *BEAUTIFUL* human beings. My eyes swell with tears when I think of how much love I have in the heart of mine for y'all.

No, wait... I'm sorry... That was just something in my eye.

Well, none-the-less >> YOU ROCK!!! :D

I [HEART] XmlTeam!

O'Reilly XML Blog — Wed, 31 Jan 2007 05:35:03 GMT

XmlTeam may not be much to look at, XmlTeam But at this moment in time, by golly, I believe he/she is the most *BYOO-T-FULL* person in the world, Monday, January 29, 2007 2:30 PM by XmlTeam Microsoft XML Team's WebLog...

re: XSLT 2.0

mikechampion — Wed, 31 Jan 2007 07:09:10 GMT

And we worried that M. David would hate us because XSLT2 wouldn't ship in Orcas :=)

re: XSLT 2.0

xmlhacker — Wed, 31 Jan 2007 08:02:53 GMT

>> And we worried that M. David would hate us because XSLT2 wouldn't ship in Orcas :=)

Nothing but love, Mike! Nothing but love :D

Thanks for bringing this all together, btw... Obviously a lot more has gone into all of this than what can be seen at the surface level, but none-the-less, your role in bringing this all together is both obvious and appreciated (as are the efforts of those that might not be so obvious from the outside looking in)!

re: XSLT 2.0

mikechampion — Wed, 31 Jan 2007 08:24:01 GMT

M. David was right in his O'Reilly blog ... credit the people who " kick, scream, and cry loud enough" not any particular person in Redmond. For example, we've noted how many comments Ralf gets on his LINQ to XSD posts. If you want us to do something new or different in the core XML technology area, you know what to do: comment here, post a private message to http://blogs.msdn.com/xmlteam/contact.aspx, blog about it, or do something else to make your opinion heard.

XSLT 2.0, XPath 2.0 e XQuery 1.0

Paolo Pialorsi — Wed, 31 Jan 2007 16:53:11 GMT

Mi unisco alla soddisfazione del XmlTeam di Microsoft , nell'annunciare la nascita della W3C Recommendation

re: XSLT 2.0

Mike — Wed, 31 Jan 2007 20:39:58 GMT

"Our users have made it very clear that they want an XSLT 2.0 implementation once the Recommendation is complete. "

This is indeed the correct way to do it, instead of implementing draft-specs. It will probably be quite a while till we get to play with it, but it will be great :)

re: XSLT 2.0

Mike Champion — Thu, 01 Feb 2007 00:25:02 GMT

Just to be clear: IMPLEMENTING draft specs makes perfect sense to help out the group writing the spec. For an odd combination of historical [we originally bet on XQuery for the XSLT2 niche :-) ] and organizational reasons that didn't happen here, Nobody from Microsoft was involved in the drafting of the XSLT2 spec per se, although we participated in the development of XPath2 and the functions/operators via the XQuery WG.

SHIPPING anything but a final Recommendation in a core technology, on the other hand, is a Very Bad Idea, a lesson Microsoft learned painfully with the non-final version of XSLT that shipped in IE 5. Several DBMS vendors, including Microsoft, did ship implementations of XQuery drafts. The SQL Server people considered that less problematic because a) only very core subset of features less likely to be revised was supported; b) there is a smaller and more specialized customer base for XQuery in the DB than XSLT in the .NET framework; and c) it really was needed to meet strong customer demand.

re: XSLT 2.0

XSLTplusSQLServer Guy — Thu, 01 Feb 2007 18:57:33 GMT

This is excellent news. I have already worked with Saxon XSLT2 on my Sun platform and I have to say that reverting back to XSLT1 on MS is a real pain.

XSLT 2.0

Michael Flanakin — Fri, 02 Feb 2007 21:25:48 GMT

re: XSLT 2.0

Manfred Staudinger — Fri, 02 Feb 2007 23:00:16 GMT

"The eventual release date and ship vehicles (e.g. a future version of .NET or a standalone release over the Web) have not been determined, and depend on technical progress, customer demand, and other currently unknowable factors."

Please also consider upgrading XSLT in Internet Explorer

re: XSLT 2.0

XmlTeam — Fri, 02 Feb 2007 23:30:57 GMT

We are discussing whether to implement XSLT2 in the native stack (MSXML3 and MSXML6). The needs of IE are the biggest consideration (it uses the native libraries), and we will definitely coordinate with the IE team.

re: XSLT 2.0

Kurt Cagle — Mon, 05 Feb 2007 10:58:48 GMT

This has to be one of the most exciting pieces of news I've seen coming from Microsoft in a long, long time! Mike Champion, thank you for this - I too look forward to XSLT 2.0 being an integral part of the Microsoft Core XML Foundation.

re: XSLT 2.0

Rob Grainger — Mon, 05 Feb 2007 14:29:32 GMT

Please, please support this in the native stack. It makes a lot of sense to have the same features for XML standards available from both COM and .NET world.

re: XSLT 2.0

Scott Trenda — Mon, 05 Feb 2007 18:34:52 GMT

THANK YOU SO MUCH. I've found MSXML to be the most robust XSLT 1.0 processor out there, and the company I work for won't take anything less. I'm giddy with anticipation of your XSLT2 implementation - the rest of us (and not just those with access to bleeding-edge XML technology) will FINALLY be able to access this great tool!

And, y'know, a huge thank you to the W3C for finally releasing these three as an official recommendation. :D

re: XSLT 2.0

Dan McCreary — Wed, 07 Feb 2007 01:34:15 GMT

Awesome!

Thanks for getting the XSLT 2.0 rolling. It is a great step in the right direction. I have been using various versions of XSLT 2.0 for almost three years and find it to be a great productivity boost.

PS Any word on when you will have support for XForms? This has been a w3c Recommendation for a while now.

It's October, 2007: Do You Know Where Your Microsoft XSLT 2.0 CTP Release Is?

O'Reilly XML Blog — Thu, 04 Oct 2007 14:57:39 GMT

June 13th, 2006 Chances are zero for XSLT2 in Orcas. Orcas is spec frozen now, and we can't do a lot of work hoping that W3C will finalize the spec before we finalize the code. Also, Orcas is a tools...

Microsoft XML Team's WebLog : XSLT 2.0

Relationship Compatibility — Sun, 08 Jun 2008 13:18:41 GMT

We are pleased to note that XSLT 2.0 and XPath 2.0 are now W3C Recommendations . Microsoft contributed thousands of person-hours to the W3C efforts that developed these standards and is committed assist with the further development of XML standards a