Subject: Re: [xsl] XSLT 2.0 empty string From: David Carlisle <davidc@xxxxxxxxx> Date: Mon, 28 Feb 2005 14:13:04 GMT |
Michael wrote There's actually nothing specific to XSLT 2.0 here: these are all 1.0 expressions where 2.0 gives the same result as 1.0 As with XPath 1.0, when you compare a set of things to a single thing, the result is true if there is at least one match. I think the point of the example was that the expectation was that the variable didn't have a set (sequence) semantic but rather was a string as if string($f) had been applied, due to the as attribute on the xsl:variable (which is a 2.0 feature of course). But I think it's true to say that as="xs:string" does _not_ force an empty sequence to coerce to an empty string, isn't it? David ________________________________________________________________________ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] XSLT 2.0 empty string, Michael Kay | Thread | RE: [xsl] XSLT 2.0 empty string, Michael Kay |
RE: [xsl] XSLT 2.0 empty string, Michael Kay | Date | [xsl] nodeSet saxon, Eder de Oliveira |
Month |