- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 20 Oct 2009 11:14:45 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7976 Summary: [XSLT 2.1] xsl:analyze-string applied to an empty sequence Product: XPath / XQuery / XSLT Version: Working drafts Platform: PC OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: XSLT 2.1 AssignedTo: mike@saxonica.com ReportedBy: mike@saxonica.com QAContact: public-qt-comments@w3.org The new fn:analyze-string() function behaves like most string functions in that it accepts an empty sequence as input, and treats it in the same way as a zero-length string (in both cases the output will be an empty fn:analyze-string-result element). The xsl:analyze-string instruction in XSLT 2.0 does not work this way: it reports an error if the input is an empty sequence. So, for example, if there is no address element then <xsl:analyze-string select="address"> will cause a type error, but if the address element is present and empty, it will produce empty output. I propose we change this (a) for usability, (b) for consistency, and (c) to make it a little bit easier for implementations to reuse code between xsl:analyze-string and fn:analyze-string. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 20 October 2009 11:14:49 UTC