This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title
links to the most recent version of a document.
For related introductory information, see: Query, Transformation.
Completed Work
W3C Recommendations have
been reviewed by W3C Members, by software developers, and by other
W3C groups and interested parties, and are endorsed by the
Director as Web Standards. Learn more about the W3C Recommendation
Track.
Group Notes are not standards and do not
have the same level of W3C endorsement.
Standards
|
2011-03-17
|
translations
·
errata
This document defines the syntax and formal semantics of XQuery
and XPath Full Text 1.0 which is a language that extends XQuery 1.0
[XQuery 1.0: An XML Query Language] and XPath
2.0 [XML Path Language (XPath) 2.0] with
full-text search capabilities.
|
|
2010-12-14
|
translations
·
errata
XPath is a way to refer to parts of an XML document.
XPath 2.0 is based on the XQuery 1.0 and XPath 2.0 Data Model (XDM),
and also introduces Schema awareness and data typing.
|
|
2010-12-14
|
translations
·
errata
This document defines the W3C XQuery 1.0 and XPath 2.0 Data
Model (XDM), which is the data model of [XPath
2.0], [XSLT 2.0], and [XQuery], and any other specifications that reference
it. This data model is based on the [XPath
1.0] data model and earlier work on an [XML
Query Data Model]. This document is the result of joint work by
the [XSL Working Group] and the [XML Query Working Group].
|
|
2010-12-14
|
translations
·
errata
This document defines formally the semantics of XQuery 1.0 [XQuery 1.0: An XML Query
Language]
and
XPath 2.0 [XML Path Language (XPath)
2.0].
|
|
2010-12-14
|
translations
·
errata
This document defines constructor functions, operators and
functions on the datatypes defined in [XML
Schema Part 2: Datatypes Second Edition] and the datatypes
defined in [XQuery 1.0 and XPath 2.0
Data Model]. It also discusses functions and operators on nodes
and node sequences as defined in the [XQuery 1.0 and XPath 2.0 Data Model]. These
functions and operators are defined for use in [XML Path Language (XPath) 2.0], [XQuery 1.0: An XML Query Language] and [XSL Transformations (XSLT) Version 2.0] and other
related XML standards. The signatures and summaries of functions
defined in this document are available at: http://www.w3.org/2005/xpath-functions.
|
|
1999-11-16
|
errata
This is the original version of XPath from 1999; some
implementations are still stuck on this, and some
specifications still refer to it. For new work
you should consider XPath 2 instead.
|
Group Notes
|
2011-01-25
|
The document specifies requirements for Full-Text Search for use
in XQuery [XQuery] and XPath [XPath].
|
|
2011-01-25
|
This document specifies usage scenarios for full-text queries as
part of XML Query [XQuery 1.0: An XML Query
Language] and XPath [XML Path Language
(XPath) 2.0].
|
|
2004-02-26
|
How to use XPath with the DOM.
|
Drafts
Below are draft documents:
Last Call Drafts, other Working Drafts.
Some of these may become Web Standards through the W3C Recommendation Track
process. Others may be published as Group Notes or
become obsolete specifications.
Last Call Drafts
|
2011-12-13
|
XPath 3.0 (renamed from XPath 2.1 to align with the family of "3.0"
specifications) is an expression language that allows the processing
of values conforming to the data model defined in [XQuery and XPath
Data Model (XDM) 3.0]. Some of the important new features since XPath 2.0 are:
- Literal function items, inline functions, dynamic function
invocations, and function item coercion
- Clarification of rules associated with sequence type matching
- let expressions
- EQNames (QNames with a namespace URI instead of a namespace prefix)
- Support for union types in casting and function arguments
|
|
2011-12-13
|
XPath and XQuery Functions and Operators 3.0 (renamed from XPath and
XQuery Functions and Operators 1.1 to align with the family of "3.0"
specifications) defines a library of functions available for use in
XPath 3.0, XQuery 3.0, and XSLT 3.0. Some of the new features since
XPath 2.0 and XQuery 1.0 Functions and Operators include:
- More than 30 new functions have been added, including functions
transferred from the XSLT 2.0 specification into Functions and
Operators 3.0 and additional versions of existing functions with
different signatures
- The syntax for regular expressions was enhanced to allow for
non-capturing groups; additionally, a new flag value was added for
regular-expression-related functions that accept a flag argument
- Support for function items has been added in the form of a number
of new functions
- The description of fn:error was rewritten to accommodate the
addition of try/catch capabilities in XQuery 3.0
|
|
2011-12-13
|
XPath and XQuery Data Model (XDM) 3.0 (renamed from XPath and XQuery
Functions and Operators (XDM) 1.1 to align with the family of "3.0"
specifications) defines the data model on which all operations of
XPath 3.0, XQuery 3.0, and XSLT 3.0 operate. In this version of XDM,
two new data types have been added:
- From XML Schema 1.1 Part 2 (Datatypes), the xs:dateTimeStamp data type
- To support XPath 3.0's and XQuery 3.0's function item capabilities,
a function item data type
|
Other Working Drafts
|
2011-12-13
|
This document defines the syntax and formal semantics of XQuery
and XPath Full Text 3.0, which is a language that extends XQuery 3.0
[XQuery 3.0: An XML Query Language] and XPath 3.0 [XML Path Language
(XPath) 3.0] with full-text search capabilities.
|
Obsolete Specifications
These specifications have either been superseded by others,
or have been abandoned. They remain available for archival
purposes, but are not intended to be used.
Retired
|
2005-06-03
|
Requirements for version 2.0 of XPath;
we are now working on Version 2.1.
|
|
2005-04-04
|
This document describes possible strategies for tokenizing the [XML Path Language (XPath) 2.0] and [XQuery 1.0: An XML Query Language] languages, and is provided as a helpful guide to those who are designing an implementation for these languages, and as background material for the normative EBNF found in the language specifications. In the future this document may be expanded to cover more general parsing strategies.
|
W3C
