Subject: Re: [xsl] XPath that returns nothing From: Liam R E Quin <liam@xxxxxx> Date: Wed, 28 Sep 2011 22:24:34 -0400 |
On Wed, 2011-09-28 at 12:07 +0100, David Carlisle wrote: [...] > if you have a function that expects a single > element and you go > xsl:param name="x" as="element()" > then if one of the input documents is bad the error percolates up to the > top level and not only that document fails to produce but the entire run > is aborted. So use, as="element(sockColour)?" maybe? You still get some additional sanity checking and maybe some performance benefits, with less strictness... Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] XPath that returns nothin, David Carlisle | Thread | Re: [xsl] XPath that returns nothin, David Carlisle |
Re: [xsl] [ANN] New XSL-FO 2.0 Work, Tony Graham | Date | Re: [xsl] XPath that returns nothin, David Carlisle |
Month |