- From: <bugzilla@jessica.w3.org>
- Date: Mon, 24 Aug 2015 11:02:07 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29079 Bug ID: 29079 Summary: [xslt 3.0] xsl:where-populated and empty arrays Product: XPath / XQuery / XSLT Version: Last Call drafts Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: XSLT 3.0 Assignee: mike@saxonica.com Reporter: mike@saxonica.com QA Contact: public-qt-comments@w3.org Target Milestone: --- In the xsl:where-populated instruction, if XPath 3.1 is in use, an empty array should be treated as "empty" for the purposes of the xsl:where-populated instruction. This appears to be the first case where we have to consider what happens if XPath 3.1 is enabled and XPath expressions are called that return arrays. There are probably other cases, e.g. what should "constructing complex content" do if the result of the sequence constructor contains an array? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 24 August 2015 11:02:18 UTC