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

# XPath changes

The effective boolean value of an `xs:anyURI` value is now obtained as if the value were a string. This change was decided by the Working Groups in response to bug 2545.

Supplying the empty sequence as the first argument to `namespace-uri-for-prefix()` is now the same as supplying the zero-length-string: it returns the default namespace.

The `min()` and `max()` functions now return the value after numeric promotion rather than the value in the input sequence. For example, `max((3e0, 5))` returns the double value 5e0 rather than the integer value 5.

Equality comparisons between subtypes of `xs:duration` are now permitted, for example the `xdt:dayTimeDuration` value `PT0S` and the `xdt:yearMonthDuration` value `PT0M` are now equal. Previously such a comparison was an error.

The extension function saxon:deep-equal() takes a new flag "F" that treats namespace prefixes as significant when comparing two element or attribute nodes. This has been introduced to support the rules of the `isEqualNode()` method in the DOM specification.

Next