I've been following a series of posts on Oleg Tkachenko's blog with some bemusement.
In his post A
business case for XSLT 2.0? he writes
If you are using XSLT and you think that XSLT 2.0 would provide you some real
benefits, please drop a line of comment with a short explanation pleeeease. I'm collecting
some arguments for XSLT 2.0, some real world scenarios that are hard with XSLT 1.0,
some business cases when XSLT 2.0 would provide an additional value. That's really
important if we want to have more than a single XSLT 2.0 implementation...
PS. Of course I've read Kurt's "The
Business Case for XSLT 2.0" already.
Update: I failed to stress it enough that it's not
me who needs such kind of arguments. We have sort of unique chance to persuade one
of software giants (guess which one) to support XSLT 2.0 now.
In a follow up post entitled XSLT
2.0 and Microsoft Unofficial Survey he reveals which of the software giants
he is trying to convince to implement XSLT 2.0 where he writes
Moving along business
cases Microsoft seeks to implement XSLT 2.0 I'm trying to gather some
opinion statistics amongs developers working with XML and XSLT. So I'm holding this
survey at the XML Lab site:
Would you like to have XSLT 2.0 implementation in the .NET Framework?
The possible answers are:
-
Yes, I need XSLT 2.0
-
Yes, that would be nice to have
-
No, continue improving XSLT 1.0 impl instead
-
No, XSLT 1.0 is enough for me
...
Take your chance to influence Microsoft's decision on XSLT 2.0 and win XSLT 2.0
book!
My advice to Oleg, if you want to see XSLT 2.0 in the .NET Framework then gather some
like minded souls and build it yourself. Efforts like the MVP.XML
library for the .NET Framework shows that there are a bunch of talented developers
building cool enhancements to the basic XML story Microsoft provides in the .NET Framework.
I'm not sure how an informal survey in a blog would convince Microsoft one way
or the other about implementing a technology. A business case to convince a product
team to do something usually involves showing them that they will lose or gain significant
marketshare or revenue by making a technology choice. A handful of XML geeks
who want to see the latest and greatest XML specs implemented by Microsoft does not
a business case make. Unfortunately, this means that Microsoft will tend to be
a follower and not a leader in such cases because customer demand and competitive
pressure don't occur until other people have implemented and are using the technology.
Thus if you want Microsoft to implement XSLT 2.0, you're best bet is to actually have
people using it on other platforms or on Microsoft platforms who will clamor for better
support instead of relying on informal surveys and comments in your blog.
Just my $0.02 as someone who used to work on the XML team at Microsoft.