SAXONICA

Saxon Documentation
Full Contents
About Saxon
Changes in this Release
| 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
The XPath API
Saxon on .NET
Extensibility
Saxon Extensions
Sample Saxon Applications
The Saxon SQL Extension
XSLT Elements
XPath 2.0 Expression Syntax
Function Library
Standards Conformance

# Changes to Functions and Operators

The new rules for effective boolean value, and for the `boolean()` function, have been implemented. These rules make it a type error to ask for the effective boolean value of anything other than a sequence starting with a node, or a singleton boolean, number, or string. For example, testing the effective boolean value of an `xs:anyURI` value or of a sequence of integers is now an error.

Saxon's two native tree models now implement the W3C `xml:id` proposal. An attribute named `xml:id` is considered to be an ID attribute for the purposes of the id() function. Note that when using schema or DTD validation, the attribute is not permitted unless the element declaration explicitly allows it, and it must then be declared as of type ID.

The new function `prefix-from-QName` is implemented.

In the TinyTree model, the base URI of a processing instruction is now maintained, and is accessible to the `base-uri()` function. Previously, the base URI was always taken to be the same as that of the parent element or document node.

Casting or constructing a QName or NOTATION is now permitted only if the argument is supplied as a string literal. (Saxon is actually a bit more flexible than this, and allows a compile-time expression.)

Next