Lists Home |
Date Index |
On 4/20/05, Jonathan Robie <firstname.lastname@example.org> wrote:
>. I'm trying to figure out
> why we're getting such different feedback from the hundreds of
> customers we are working with.
I'm certainly not suggesting that DataDirect (or Saxon/Saxon.NET for
that matter) users don't have a good use case for XQuery on the
client/mid-tier, simply that the demand for it in .NET framework
itself is not at all obvious. To be blunt, we need a LOT more than
"hundreds" of users to justify the investment.
I'd be happy to be wrong about this (being an XQuery "stakeholder"
myself). Also, I had been arguing that XQuery is more grokkable by
ordinary mortals than XSLT for years, so being wrong now would mean
that I was right for the previous 5 years :-)
> Our growing beta list for DataDirect XQuery suggests that there really
> is a demand for this kind of product in the Java space. Can it really
> be that different in the .NET space?
All I know is that before my time at MS, there was a heavy commitment
to the XQuery client story, and a preview release in the first beta
of .NET 2.0. This didn't generate much momentum, but did generate a
real youknowwhat-storm of protest from XSLT users who preferred XSLT2
support to XQuery support. Perhaps fortunately for our group, neither
was a Recommendation by spec freeze, so it was easy to decide that
neither go into .NET 2.0. Will one or both go into a subsequent
version? Beats me ... but part of my job is to listen for customer
demand. I'm hearing it lound and clear for XSLT 2 .... and I'm
hearing it for XQuery as the interface to XML DBMS or XML types in an
RDBMS, but I'm not hearing it for XQuery on the client. Maybe you
have done such a good job of evangelizing the idea the potential users
are all planning to buy yours?
Or maybe this is a nice niche for you folks, but not a core
infrastructure piece for Joe Developer. Time will tell. Maybe
Liam will be right and XQuery will become the Perl for data