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 in Schema-aware Processing

The error condition that occurs when a path expression such as `a/b/c` is used, and the schema definition for `b` does not allow a child named `c`, is in most cases replaced by a warning. This is because it is possible that the source document will have been validated against a schema containing a complex type derived by extension from the statically-known type of `b`, in which `c` is a permitted child. The same applies to attributes.

This also applies to element construction where a child element is constructed whose name is not permitted by the type of the parent element.

Next