Search results
Results From The WOW.Com Content Network
The XPath syntax is designed to mimic URI (Uniform Resource Identifier) and Unix-style file path syntax. More complex expressions can be constructed by specifying an axis other than the default 'child' axis, a node test other than a simple name, or predicates, which can be written in square brackets after any step. For example, the expression
XPointer is a system for addressing components of XML-based Internet media. It is divided among four specifications: a "framework" that forms the basis for identifying XML fragments, a positional element addressing scheme, a scheme for namespaces, and a scheme for XPath-based addressing.
The XQuery and XPath Data Model (XDM) is the data model shared by the XPath 2.0, XSLT 2.0, XQuery, and XForms programming languages. It is defined in a W3C recommendation . [ 1 ] Originally, it was based on the XPath 1.0 data model which in turn is based on the XML Information Set .
Compared to XPath 2.0, XPath 3.0 adds the following new features: . Inline function expressions Anonymous functions can be created in an expression context. For example, the expression function ($ a as xs:double, $ b as xs:double) as xs:double {$ a * $ b} creates a function that returns the product of its two arguments.
The "/" operator is generalized in XPath 2.0 to allow any kind of expression to be used as an operand: in XPath 1.0, the right-hand side was always an axis step. For example, a function call can be used on the right-hand side. The typing rules for the operator require that the result of the first operand is a sequence of nodes.
XSLT 3.0 will work with either XPath 3.0 or 3.1. In the case of 1.0 and 2.0, the XSLT and XPath specifications were published on the same date. With 3.0, however, they were no longer synchronized; XPath 3.0 became a Recommendation in April 2014, followed by XPath 3.1 in February 2017; XSLT 3.0 followed in June 2017.
Below are a few examples of how XQuery can be used: Extracting information from a database for use in a web service. Generating summary reports on data stored in an XML database. Searching textual documents on the Web for relevant information and compiling the results. Selecting and transforming XML data to XHTML to be published on the Web.
The fourth technology platform is JavaScript. Previously the open-source XSLT processor Saxon-CE was cross-compiled from the common Java source using GWT. SaxonJS is a completely new implementation in JavaScript. The XSLT sources can either be compiled using Saxon-EE or using a built-in XSLT-based XSLT compiler, which creates less optimized code.