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

# Changes to Saxon Extensions

Two new extension functions have been introduced: `saxon:base64Binary-to-string()` and `saxon:hexBinary-to-string()`. These represent the inverse of the two functions `saxon:string-to-base64Binary` and `saxon:string-to-hexBinary()` introduced in Saxon 8.4: they allow a `base64Binary` or `hexBinary` value to be treated as a representation of the octet sequence that results from encoding a string using a specified encoding. They were introduced because they were found useful in handling LDIF (LDAP interchange format) files.

The extension function `saxon:try` (which is available in Saxon-SA only) has been enhanced to make error information available. This is achieved by turning it into a higher order function. If the second argument is supplied as a reference to a function, the nominated function is called when an error occurs, and receives as an argument an element giving information about the error that occurred, including the error code, error message, and the location of the error in the source stylesheet or query. For more details see saxon:try().

A pair of extension functions has been added allowing an XSLT transformation to be invoked from another transformation or from a query. This now allows XSLT code to be invoked from XQuery code for the first time. The function `saxon:compile-stylesheet()` takes as input a document node at the root of a document containing a stylesheet (which may either be read from a source file using the `doc()` function, or constructed programmatically); this function returns a representation of the compiled stylesheet. The second extension function, `saxon:transform`, takes as input a compiled stylesheet and a node that acts as the initial context node of the transformation, and it returns the principal result document of the transformation. For further details see saxon:compile-stylesheet() and saxon:transform().

Next