W3C home > Mailing lists > Public > public-qt-comments@w3.org > February 2016

[Bug 29434] New: [XSLT30] xsl:on-empty/on-non-empty with attributes and use-attribute-sets

From: <bugzilla@jessica.w3.org>
Date: Mon, 08 Feb 2016 17:19:47 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29434-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29434

            Bug ID: 29434
           Summary: [XSLT30] xsl:on-empty/on-non-empty with attributes and
                    use-attribute-sets
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: mike@saxonica.com
          Reporter: abel.braaksma@xs4all.nl
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

I think the text on xsl:on-empty (section 8.4.2), and by extension
xsl:on-non-empty is not entirely unambiguous with respect to attributes:

  <empty xsl:use-attribute-sets="a">
    <xsl:on-empty select="42"/> 
  </empty>

vs

  <empty x="y">
    <xsl:on-empty select="42"/> 
  </empty>

vs

  <empty>
    <xsl:attribute name="x">y</xsl:attribute>
    <xsl:on-empty select="42"/> 
  </empty>

The way I read the spec is that the first two examples will activate the
xsl:on-empty instruction, and the last example will not. This may be surprising
and perhaps we should mention that.

Esp. wrt to use-attribute-sets, one could argue that it becomes part of
creating the sequence constructor content, in which case it should *not*
activate xsl:on-empty.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 8 February 2016 17:19:51 UTC

This archive was generated by hypermail 2.3.1 : Monday, 8 February 2016 17:19:52 UTC