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

# Serialization

The list of attributes that are considered to be URI attributes and therefore to be escaped by the HTML and XHTML output methods has been aligned with the list that is now published in the serialization spec. However, Saxon continues to escape the `name` attribute of the `a` element, which is not present in this list, because the HTML specification recommends doing so in Appendix B.2.1.

In the XML and XHTML output methods, error SEPM0004 is now reported if a `standalone` attribute or a `DOCTYPE` declaration is requested and the result tree is not a well formed XML document.

Error SESU0006 is now reported if an XML version other than "1.0" or "1.1" is requested. (It's not entirely clear that this is the right error code, there is some confusion in the spec.)

Error SEPM0009 is now detected and reported: this concerns situations under which it is not appropriate to omit the XML declaration.

Error SEPM0010 is now reported if `undeclare-prefixes="yes"` is set when the XML version is 1.0.

Next