I [HEART] XmlTeam!

by M. David Peterson

Update: via a follow-up comment from Mike Champion (to the post linked to below),

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.

Or, in other words, if you don't ask, you're a lot less likely to get what you think you might want. Kicking, screaming, and crying (if necessary) can be helpful too ;) But unless you're okay with being referred to as "that punk a$$ hacker with an attitude (who throw's tempter tantrum's if/when he doesn't get his way!)" (which I'm personally okay with, btw...) then I don't (necessarily) recommend its usage.

That said... Much like the choice of when to use SOAP over REST, or JSON over XML, use the tool that works (best) to get the job at hand done. I'll leave the decision of which tool to use when as an exercise for the reader. ;)

[Original Post]

XmlTeam may not be much to look at,


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 : XSLT 2.0

Our users have made it very clear that they want an XSLT 2.0 implementation once the Recommendation is complete. A team of XSLT experts is now in place to do this, the same people who have been working on the XSLT enhancements that will be shipped in the forthcoming "Orcas" release of Visual Studio / .NET 3.5. Orcas development work is winding down in advance of Beta releases over the next several months, so there is no possibility of shipping XSLT 2.0 in Orcas. The XSLT team will, however, be putting out Community Technology Previews (CTP) with the XSLT 2 functionality and appropriate tooling as the implementation matures. 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.

We very much wish to hear from our user community about their requirements that could be met with XSLT 2.0. We can discuss how to address those requirements in this interim period with existing technologies and those that will be released in "Orcas". Those who urgently need an implementation of that runs in the .NET environment may wish to check out the Saxon open source project or the schema-aware commercial version produced by Saxonica

So what kills me about all of this (the above "event" had been previously known to be in the works, so its of no great shock) is contained in the comment section of the above linked post,