XQuery has now reached standardization by the W3C. The XML Team at Microsoft is now asking for input on whether there should be a standalone XQuery implementation in the .Net Framework in their blog entitled Standalone XQuery Implementation in .NET?.

My posted response is below:

I, also, would like to see an XQuery implementation within the .Net Framework.

If available, I would be more inclinded to use XQuery over XSLT, particularly in a more dynamic setting to extract data, and then to shape the output before consuming within an application.

While the XQuery implementation in SQL Server 2005 is excellent, it is still only a subset of the standard, for example, the ability to query against multiple documents. And, I would prefer to see the implementation as native to the .Net Framework, rather than as a commercial add-on.

The differences between what could be and what is available now are two fold. First, the current implementation resides on server-side, within the SQL Server itself. A .Net Framework (System.XML.XQuery) implementation would allow the developer to choose where the query would be executed. Additionally, you would be able to query across multiple documents, which you cannot do in the SQL Server 2005 version.

I have found the XQuery syntax to be easier to craft to extract XML content and shape the output than using XSLT. I think there is a strong incentive to have the XQuery implementation because it can provide some features that may either be missing or are easier to use than SQL Server XQuery, LINQ or XSLT.

I vote "Yes" to XQuery in the .Net Framework.

I gave a presentation on XQuery at the NovaSQL user group that meets in Vienna, Virginia.

Jeremy Kadlec and Brian Moran run a great program. The turnout was very good, too. Lots of SQL experts.

Do you know how you can tell if you are giving a presentation to people that are SQL experts? You can tell that they are when you try to do a SELECT statement, and you get the dreaded Invalid object name error. Before you can blink you hear twenty-thirty voices saying, "You're in the Master database!"

I had a great deal of fun talking about XQuery with a very savvy crowd.

Attached to this post are my PowerPoint slides from the presentation.

OK, this is my own personal opinion, but I think it is in Microsoft's best interest to have people on standards committees and working groups, like the World Wide Web (W3C).

I imagine that it might be uncomfortable for Microsoft and its managers to have staff that both pursue work on Microsoft projects and also work on standards committes. Not only is there the issue of dividing time with your valuable resources (i.e. your employee), but also there may be times when the standards work against Microsoft.

However, that being said, as a programmer and developer, I am more apt to embrace technologies that work with open standards - not necessarily open source - then those that don't. Politically, it is a good move for Microsoft - I think it helps with acceptance of the product and tools. And, on a personal level, I hold in high esteem those folks that are working hard to come up with the standards so that systems can be built that are flexible, consistent, and can communicate. I imagine that it is not easy to work in such a compromising environment, but i am confident that the results will yield better tools for us developers.

Like it or not, it is the developers, and others down at the code or hardware level, who will always be the evangelists for technologies. I've rarely ever met a manager that was. If Microsoft relies on managers to be its guide, then it will lose its passion and the passion of its developer community, and become just another company. But "playing nice" in a cooperative manner with standards groups is one way to keep that passion alive...and I applaud Microsoft for its involvement and hope they continue to do so.