For the integration of data there are many techniques of using SQLXML and .net the sql client data provider supports execute xml reader it can consume directly the result of it to do the xml query the user can use xml directly, the role of XML query in reinventing the wheel is very large the overlap between the xquery and xslt is too great for W3C to recommend both as separate languages if the XSLT is not considered enough as an XML query language then its development should be built from the same and semantic syntactic base as XSLTThe most
"When Internet Explorer 5.0 was first shipped in 1998, Microsoft shipped an implementation of XSL that was based on the current working draft of XSL at that time. Millions of copies of this XML/XSL processor were burned on CDs and were installed on systems all around the world. Since then, the XSLT specification changed very significantly (even the namespace changed!) and was finalized. So the situation as it is today (12/4/2000) is that there are millions of copies of a parser out there which does not (by default) support the latest XSLT
This article provides a brief tour through some of the new features in XPath 2.0. It assumes that you already have a basic understanding of XPath 1.0, and that you've most likely used it in the context of XSLT. It is by no means an exhaustive overview but merely points out some of the most noteworthy features.
Relationship between XPath 1.0 and XPath 2.0
Both the XPath 1.0 recommendation and the latest XPath 2.0 working draft say that "XPath is a language for addressing parts of an XML document". This was a fairly appropriate characterization of
RSS/XML