This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28763 - [XSLT30] Following-siblings of xsl:assert should only be evaluated when xsl:assert succeeds
Summary: [XSLT30] Following-siblings of xsl:assert should only be evaluated when xsl:a...
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-04 19:54 UTC by Abel Braaksma
Modified: 2015-10-29 09:50 UTC (History)
0 users

See Also:

Attachments

Description Abel Braaksma 2015-06-04 19:54:23 UTC 
This bug originated in the mail, discussion started with https://lists.w3.org/Archives/Member/w3c-xsl-wg/2015May/0007.html (member only).

This bug was discussed and its resolution as mentioned in that mail was ACCEPTED by the WG at the 2015-06-04 telcon, minutes: https://lists.w3.org/Archives/Member/w3c-xsl-wg/2015Jun/0011.html

Summary:

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.

Resolution:

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 stylesheet.

Examples of this proposal can be found in the original mail-thread.
Comment 1 Michael Kay 2015-06-05 13:25:57 UTC 
The change has been applied.