W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2015

[Bug 28763] New: [XSLT30] Following-siblings of xsl:assert should only be evaluated when xsl:assert succeeds

From: <bugzilla@jessica.w3.org>
Date: Thu, 04 Jun 2015 19:54:23 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28763-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 28763
           Summary: [XSLT30] Following-siblings of xsl:assert should only
                    be evaluated when xsl:assert succeeds
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          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

This bug originated in the mail, discussion started with
https://lists.w3.org/Archives/Member/w3c-xsl-wg/2015May/0007.html (member

This bug was discussed and its resolution as mentioned in that mail was
ACCEPTED by the WG at the 2015-06-04 telcon, minutes:


In the aforementioned mail thread and following discussion in the WG telcon, it
was recognized that xsl:assert as it is currently written, is not very helpful
and leads to unwieldy programming with xsl:choose and xsl:if in cases where you
want to assert a pre-condition of a sequence constructor. It was precisely this
scenario that the original idea of xsl:assert was supposed to remedy.


Following the CONCLUSION from the 2015-06-04 it was ACCEPTED that xsl:assert
statements should be evaluated *prior* to their following siblings in the XSLT

Examples of this proposal can be found in the original mail-thread.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 4 June 2015 19:54:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:54 UTC