SAXONICA

Saxon Documentation
Full Contents
About Saxon
Changes in this Release
» | Version 8.9 (2007-02-12)
| Version 8.8 (2006-09-05)
| Version 8.7.3 (2006-06-13)
| Version 8.7.2 (2006-04-19)
| Version 8.7.1 (2006-04-13)
| Version 8.7 (2006-02-24)
| Version 8.6.1 (24 November 2005)
| Version 8.6 (3 November 2005)
| Version 8.5.1 (26 August 2005)
| Version 8.5 (2 August 2005)
| Version 8.4 (4 April 2005)
| Version 8.3 (11 February 2005)
| Version 8.2 (21 December 2004)
| Version 8.1.1 (8 October 2004)
| Version 8.1 (24 September 2004)
| Version 8.0 (1 June 2004)
Conditions of Use
Using XSLT 2.0
Using XQuery
Handling Source Documents
XML Schema Processing
XPath API for Java
Saxon on .NET
Extensibility
Saxon Extensions
Sample Saxon Applications
The Saxon SQL Extension
XSLT Elements
XPath 2.0 Expression Syntax
Function Library
Standards Conformance

# Functions and Operators

The `fn:dateTime` function has been changed so that if either argument is an empty sequence, the result is an empty sequence. This implements a late change to the specification: see W3C bugzilla entry 3651.

The old `xdt` namespace is no longer supported. (The types previously in this namespace are now in the XML Schema namespace `http://www.w3.org/2001/XMLSchema`).

A new extension function `saxon:sort` has been introduced to allow sorting in free-standing XPath applications. There are two variants: a single argument version which simply sorts a sequence of nodes or atomic values on the value itself (after atomization in the case of a node), and a two-argument version whose second argument is an expression (obtained by calling saxon:expression()) that is used to calculate the sort key.

An enhancement to the `saxon:transform` extension function allows parameters to be supplied to the transformation. This is done by introducing an optional parameter whose value is a sequence of nodes (typically elements): the name of the node is used as the name of a parameter, and the atomized value of the node is used as the value of the parameter.

The Saxon-SA extension functions `saxon:index` and `saxon:find` have been rewritten to use the same indexing logic as is used for implicitly-created indexes. A consequence is that the order of results (which has never been well-defined) may be different from before.

The function `iri-to-uri()` now escapes ASCII characters that are disallowed in an IRI value, specifically the characters space, double-quotation-mark, less-than, greater-than, backslash, circumflex, grave accent, left curly brace, vertical bar, and right curly brace.

Next