<?xml version="1.0" encoding="iso-8859-1"?>
<?xml-stylesheet href="../../make-menu.xsl" type="text/xsl"?><html>
<head>
<this-is section="changes" page="intro93" subpage="xpath20-93"/>
<!--
Generated at 2011-12-09T20:47:22.916Z--><title>Saxonica: XSLT and XQuery Processing: XPath 2.0 and XQuery 1.0 changes</title>
<meta name="coverage" content="Worldwide"/>
<meta name="copyright" content="Copyright Saxonica Ltd"/>
<meta name="title"
content="Saxonica: XSLT and XQuery Processing: XPath 2.0 and XQuery 1.0 changes"/>
<meta name="robots" content="noindex,nofollow"/>
<link rel="stylesheet" href="../../saxondocs.css" type="text/css"/>
</head>
<body class="main">
<h1>XPath 2.0 and XQuery 1.0 changes</h1>
<p>Erratum XQ.E34 is implemented. This affects what can appear after a "/" at the start of an expression. Certain constructs that can appear at the start
of a relative path expression are now recognized, when they were previously rejected as errors: for example <code>/element{a}{b}</code> or <code>/<a class="bodylink"/></code>
or <code>/unordered{x}</code>. Some other constructs that were previously accepted are now rejected, for example <code>/ instance of document-node()</code> (this
must now be written <code>(/) instance of document-node()</code>).</p>
<p>In XQuery 1.0 and XQuery 1.1, the pragmas <code>saxon:stream</code> and <code>saxon:validate-type</code> are now ignored (with a warning) if running
Saxon-HE or Saxon-PE. Previously they caused a static error.</p>
<table width="100%">
<tr>
<td>
<p align="right"><a class="nav" href="xquery30-93.xml">Next</a></p>
</td>
</tr>
</table>
</body>
</html>
