The following defects have been cleared in Saxon 8.1:
Under various circumstances (especially with DOM and JDOM sources) Saxon may fail
with the message "Unknown type annotation 0"
The format-date() function gets the day of the week wrong when using the [F] option.
The -s option on the XQuery command line does not work unless the -wrap option is used;
the corresponding facility in the Java API doesn't work either
A NullPointerException can occur in XQuery when an empty element constructor is used
as part of an expression, for example "/."
A ClassCastException can occur while optimizing the expression used to initialize a global
variable in XQuery.
An internal error can occur in XQuery, with the error
message "Children of an ExprInstruction must themselves be ExprInstructions".
The schema processor does not allow an xs:annotation element to appear as a child
of xs:include or xs:import.
A NullPointerException occurs if the second argument of an arithmetic operator is the empty
The Saxon schema processor does not handle xs:notation; this is a documented restriction,
but the processor instead of recovering cleanly fails with an exception when xs:notation is encountered.
The Saxon schema processor validates the xs:minInclusive facet incorrectly, leading to
spurious error messages.
Spurious static type errors may be reported when the static type
of an operand is xdt:untypedAtomic.
Variables used in match patterns can corrupt the caller's stack frame.
A NullPointerException occurs when comparing two QNames if either is in no namespace.
An infinite loop occurs getting the base URI of a node in a DOM or JDOM tree.
The stack frame allocated for saxon:evaluate() may be too small, leading to an
When (in XSLT) character maps are used with the text output method, spurious spaces
appear in the output.
A ClassCastException occurs if an XPath expression evaluated using the Java XPath API
returns a date or time value.
A NullPointerException occurs if an XPath expression evaluated using the Java XPath API
requires access to the default collation.
When the count() function is applied to an expression that selects a sub-range of a sequence,
the wrong answer is given.
The namespace-uri() function can give the wrong answer when the source is a DOM source.
Two nodes in different DOM documents may share the same identity.
The XQuery API does not validate the values of serialization parameters.
This is a duplicate of 979108.
The schema processor does not handle recursive xs:import elements.
In XQuery, the default element namespace (as used for path expressions)
is not reset when it goes out of scope.
In the schema processor, the specification mixed="yes" on a complex type is not inherited
on another type derived from that type by extension.