XQuery is a functional, side effect-free, expression-oriented programming language with a simple type system, summed up by Kilpeläinen:{{Cite journal| doi = 10.1002/spe.1140| title = Using XQuery for problem solving| journal = Software: Practice and Experience| volume = 42| issue = 12| pages = 1433–1465| year = 2012| last1 = Kilpeläinen | first1 = Pekka| s2cid = 15561027| url = http://www.cs.uef.fi/~kilpelai/RDK11/refs/xqueryProblems.pdf}}

{{blockquote|All XQuery expressions operate on sequences, and evaluate to sequences. Sequences are ordered lists of items. Items can be either nodes, which represent components of XML documents, or atomic values, which are instances of XML Schema base types like {{mono|xs:integer}} or {{mono|xs:string}}. Sequences can also be empty, or consist of a single item only. No distinction is made between a single item and a singleton sequence. (...) XQuery/XPath sequences differ from lists in languages like Lisp and Prolog by excluding nested sequences. Designers of XQuery may have considered nested sequences unnecessary for the manipulation of document contents. Nesting, or hierarchy of document structures is instead represented by nodes and their child-parent relationships}}

XQuery provides the means to extract and manipulate data from XML documents or any data source that can be viewed as XML, such as relational databases[http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.xml.doc/doc/c0023907.html?lang=en "Data retrieval with XQuery"]. Retrieved on 18 January 2016. or office documents.

XQuery contains a superset of XPath expression syntax to address specific parts of an XML document. It supplements this with a SQL-like "FLWOR expression" for performing joins. A FLWOR expression is constructed from the five clauses after which it is named: FOR, LET, WHERE, ORDER BY, RETURN.

The language also provides syntax allowing new XML documents to be constructed. Where the element and attribute names are known in advance, an XML-like syntax can be used; in other cases, expressions referred to as dynamic node constructors are available. All these constructs are defined as expressions within the language, and can be arbitrarily nested.

The language is based on the XQuery and XPath Data Model (XDM) which uses a tree-structured model of the information content of an XML document, containing seven kinds of nodes: document nodes, elements, attributes, text nodes, comments, processing instructions, and namespaces.

XDM also models all values as sequences (a singleton value is considered to be a sequence of length one). The items in a sequence can either be XML nodes or atomic values. Atomic values may be integers, strings, Booleans, and so on: the full list of types is based on the primitive types defined in XML Schema.

Features for updating XML documents or databases, and full text search capability, are not part of the core language, but are defined in add-on extension standards: XQuery Update Facility 1.0 supports update feature and XQuery and XPath Full Text 1.0 supports full text search in XML documents.

XQuery 3.0 adds support for full functional programming, in that functions are values that can be manipulated (stored in variables, passed to higher-order functions, and dynamically called).

The sample XQuery code below lists the unique speakers in each act of Shakespeare's play Hamlet, encoded in [http://www.ibiblio.org/xml/examples/shakespeare/hamlet.xml hamlet.xml]

{

for $act in doc("hamlet.xml")//ACT

let $speakers := distinct-values($act//SPEAKER)

return

}

All XQuery constructs for performing computations are expressions. There are no statements, even though some of the keywords appear to suggest statement-like behaviors. To execute a function, the expression within the body is evaluated and its value is returned. Thus to write a function to double an input value, one simply writes:

declare function local:doubler($x) { $x * 2 }

To write a full query saying 'Hello World', one writes the expression:

"Hello World"

This style is common in functional programming languages.

{{unreferenced section|date=May 2020}}

Below are a few examples of how XQuery can be used:

1. Extracting information from a database for use in a web service.
2. Generating summary reports on data stored in an XML database.
3. Searching textual documents on the Web for relevant information and compiling the results.
4. Selecting and transforming XML data to XHTML to be published on the Web.
5. Pulling data from databases to be used for the application integration.
6. Splitting up an XML document that represents multiple transactions into multiple XML documents.

{{more citations needed section|date=May 2020}}

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 HTML 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 (XDM), type system, and function library, and both include XPath 2.0 as a sublanguage.

The two languages, however, are rooted in different traditions and serve the needs of different communities. XSLT was primarily conceived as a stylesheet language whose primary goal was to render XML for the human reader on screen, on the web (as web template language), or on paper. XQuery was primarily conceived as a database query language in the tradition of SQL.

Because the two languages originate in different communities, XSLT is stronger{{according to whom|date=May 2015}} in its handling of narrative documents with more flexible structure, while XQuery is stronger in its data handling (for example, when performing relational joins).

XSLT 1.0 appeared as a Recommendation in 1999, whereas XQuery 1.0 only became a Recommendation in early 2007; as a result, XSLT is still much more widely used. Both languages have similar expressive power, though XSLT 2.0 has many features that are missing from XQuery 1.0, such as grouping, number and date formatting, and greater control over XML namespaces.{{cite web|url=https://www.mscs.mu.edu/~praveen/Teaching/fa05/AdvDb/PaperTeams/XSLT2XQTeam/Comparing%20XSLT%20and%20XQuery.htm|title=Comparing XSLT and XQuery|first=Michael|last=Kay|date=May 2005}}{{cite web|url=http://www.xml.com/pub/a/2005/03/09/xquery-v-xslt.html|title=Comparing XSLT and XQuery|first=J. David|last=Eisenberg|date=2005-03-09}}{{cite web|url=http://www.xmlhack.com/read.php?item=1080|title=XQuery, XSLT "overlap" debated|date=2001-02-23|first=Michael|last=Smith}} Many of these features were planned for XQuery 3.0.{{cite web|url=http://www.w3.org/TR/xquery-30-requirements/|title=XQuery 3.0 requirements}}

Any comparison must take into account the version of XSLT. XSLT 1.0 and XSLT 2.0 are very different languages. XSLT 2.0, in particular, has been heavily influenced by XQuery in its move to strong typing and schema-awareness.

Usability studies have shown that XQuery is easier to learn than XSLT, especially for users with previous experience of database languages such as SQL.Usability of XML Query Languages. Joris Graaumans. SIKS Dissertation Series No 2005-16, {{ISBN|90-393-4065-X}} This can be attributed to the fact that XQuery is a smaller language with fewer concepts to learn, and to the fact that programs are more concise. It is also true that XQuery is more orthogonal, in that any expression can be used in any syntactic context. By contrast, XSLT is a two-language system in which XPath expressions can be nested in XSLT instructions but not vice versa.

XSLT is currently stronger than XQuery for applications that involve making small changes to

a document (for example, deleting all the NOTE elements). Such applications are generally handled

in XSLT by use of a coding pattern that involves an identity template that copies all nodes unchanged, modified by specific templates that modify selected nodes. XQuery has no equivalent to this coding pattern, though in future versions it will be possible to tackle such problems using the update facilities in the language that are under development.{{cite web|url=http://www.w3.org/TR/xqupdate/|title=XQuery Update Facility}}

XQuery 1.0 lacked any kind of mechanism for dynamic binding or polymorphism; this has been remedied with the introduction of functions as first-class values in XQuery 3.0. The absence of this capability starts to become noticeable when writing large applications, or when writing code that is designed to be reusable in different environments.{{Citation needed|date=May 2015}} XSLT offers two complementary mechanisms in this area: the dynamic matching of template rules, and the ability to override rules using xsl:import, that make it possible to write applications with multiple customization layers.

The absence of these facilities from XQuery 1.0 was a deliberate design decision: it has the consequence that XQuery is very amenable to static analysis, which is essential to achieve the level of optimization needed in database query languages. This also makes it easier to detect errors in XQuery code at compile time.

The fact that XSLT 2.0 uses XML syntax makes it rather verbose in comparison to XQuery 1.0. However, many large applications take advantage of this capability by using XSLT to read, write, or modify stylesheets dynamically as part of a processing pipeline. The use of XML syntax also enables the use of XML-based tools for managing XSLT code. By contrast, XQuery syntax is more suitable for embedding in traditional programming languages such as Java (see XQuery API for Java) or C#. If necessary, XQuery code can also be expressed in an XML syntax called XQueryX. The XQueryX representation of XQuery code is rather verbose and not convenient for humans, but can easily be processed with XML tools, for example transformed with XSLT stylesheets.{{cite web|url=http://www.w3.org/TR/xqueryx/|title=XML Syntax for XQuery (XQueryX)}}{{cite web|url=http://saxonica.blogharbor.com/blog/_archives/2007/1/20/2665644.html|title=Saxon diaries: How not to fold constants|author=Michael Kay}}

Two major extensions to the XQuery were developed by the W3C:

• XQuery 1.0 and XPath 2.0 Full-Text[http://www.w3.org/TR/xquery-full-text/ XQuery and XPath Full Text 1.0]
• XQuery Update Facility

Both reached Recommendation status as extensions to XQuery 1.0, but work on taking them forward to work with XQuery 3.0 was abandoned for lack of resources.

Work on XQuery 3.0 was published as a Recommendation on 8 April 2014,[http://www.w3.org/TR/xquery-30/ XML Query (XQuery) 3.0] and XQuery 3.1 is a Recommendation as at February 2017.

A scripting (procedural) extension for XQuery was designed, but never completed.[http://www.w3.org/TR/xquery-sx-10-requirements/ XQuery Scripting Extension 1.0 Requirements][https://www.w3.org/TR/2017/PR-xquery-31-20170117/ XQuery 1.0 Scripting Extension]

The EXPath Community Group[http://www.w3.org/community/expath/ EXPath Community Group] develops extensions to XQuery and other related standards (XPath, XSLT, XProc, and XForms).

The following extensions are currently available:

• Packaging System[http://expath.org/spec/pkg/20120509 Packaging System]
• File Module[http://expath.org/spec/file/20120614 File Module]
• Binary Module[http://expath.org/spec/binary/20130312 Binary Module]
• Web Applications[http://expath.org/spec/webapp/20130401 Web Applications]

JSONiq is an extension of XQuery that adds support to extract and transform data from JSON documents. JSONiq is a superset of XQuery 3.0.

It is published under the Creative Commons Attribution-ShareAlike 3.0 license.

XQuery 3.1 de facto deprecates JSONiq as it has added full support for JSON.

The EXQuery{{cite web|title=Standard for portable XQuery applications|url=http://www.exquery.org/|access-date=12 December 2013}} project develops standards around creating portable XQuery applications. The following standards are currently available:

• RESTXQ{{Cite web|url=https://exquery.github.io/exquery/exquery-restxq-specification/restxq-1.0-specification.html|title = RESTXQ 1.0: RESTful Annotations for XQuery}}

• Querying XML: XQuery, XPath, and SQL/XML in context. Jim Melton and Stephen Buxton. Morgan Kaufmann, 2006. {{ISBN|1-55860-711-0}}.
• {{cite book | last=Walmsley | first=Priscilla | date=2007 | title=XQuery, 1st Edition | publisher=O'Reilly Media | isbn=978-0-596-00634-1 }}
• {{cite book | last=Walmsley | first=Priscilla | date=2015 | title=XQuery, 2nd Edition | publisher=O'Reilly Media | isbn=978-1-4919-1510-3 }}
• XQuery: The XML Query Language. Michael Brundage. Addison-Wesley Professional, 2004. {{ISBN|0-321-16581-0}}.
• XQuery from the Experts: A Guide to the W3C XML Query Language. Howard Katz (ed). Addison-Wesley, 2004. {{ISBN|0-321-18060-7}}.
• An Introduction to the [http://www.stylusstudio.com/xquery_flwor.html XQuery FLWOR] Expression. Dr. Michael Kay (W3C XQuery Committee), 2005.

{{see also|Category:XQuery processors}}

• XQuery API for Java (XQJ) Java Specification Request

{{Reflist|2}}

• Portions borrowed with permission from the books "XML Hacks" (O'Reilly Media) and "XQuery" (O'Reilly Media).
• Previous version based on an article at the French language Wikipedia

{{Wikibooks|XQuery}}

• [http://www.w3.org/XML/Query W3C XML Query (XQuery)]

{{W3C Standards}}

{{Query languages}}

{{Authority control}}

{{DEFAULTSORT:Xquery}}

Category:Fourth-generation programming languages

Category:Functional languages

Category:Query languages

Category:World Wide Web Consortium standards

Category:XML data access