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
Debates on the XML-DEV and XSL mailing lists over the last two weeks concern the futures of XSLT, XPath, and, the latest addition to the W3C XML toolkit, XML Query. There are no signs of these debates ending this week. Discussion on XML-DEV about the design of XML Query rages on.
Reinventing the Wheel
The focus of last week's XML-Deviant was the concern expressed by several XML-DEV contributors that the interdependence of several W3C specifications may have exceeded the dictates of software reuse and become instead a tangled mess. Suggestions were
Although XQuery was initially conceived as a query language for large collections of XML documents, it is also capable of transforming individual documents. As such, its capabilities overlap with XSLT, which was designed expressly to allow input XML documents to be transformed into XML or other formats.The XSLT 2.0 and XQuery standards were developed by separate working groups within W3C, working together to ensure a common approach where appropriate. They share the same data model, type system, and function library, and both include XPath 2.0 as a
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
Abstract
XPath 2.0 is an expression language that allows the processing of values conforming to the data model defined in [XQuery/XPath Data Model (XDM)]. The data model provides a tree representation of XML documents as well as atomic values such as integers, strings, and booleans, and sequences that may contain both references to nodes in an XML document and atomic values. The result of an XPath expression may be a selection of nodes from the input documents, or an atomic value, or more generally, any sequence allowed by the data model. The name of
Abstract
XSLT 2.0 and XQuery 1.0 have been developed by two Working Groups in close collaboration, and there is a high degree of overlap in the functionality of the two languages. They share many common concepts, such as the underlying data model, and they both include the whole of XPath 2.0 as a sublanguage, together with its extensive repertoire of data types and the associated function library.
The two languages focus on different needs, and to some extent these needs exist in different user communities. This makes it understandable that many
xtensible Stylesheet Transformations, or XSLT, has received decidedly mixed reviews from developers. Although XSLT has many evangelists it has its detractors as well. Because of some concepts, such as static variables. XSLT's learning curve can also be a bit steep, particularly for some of the more complex transformations.
Many of the problems stem from a fundamental lack of understanding about how the language works. Primarily through Mulberry's XSL-List, the XSLT developer community has gone to great lengths to educate developers on how to use
This is the home page for the Open Source SAXON XSLT processor developed by Michael Kay.
See also the project page for Saxon.
The latest version of Saxon is version 8.9. This is a complete and conformant implementation of the XSLT 2.0, XQuery 1.0, and XPath 2.0 Recommendations published on 23 January 2007 by W3C. Since this is the first release published since these specifications became final Recommendations, there is a strong emphasis on conformance in this release.
Saxon 8.9 is released simultaneously by Saxonica on the Java and .NET
RSS/XML