This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
As discussed by mail (see https://lists.w3.org/Archives/Member/w3c-xsl-wg/2015Jun/0012.html, member only) and agreed in the XSLWG meeting of July 9, 2015. The default for assertions should be OFF instead of ON (current status quo).
Note, this change means it is no longer possible to control assertion enablement in this kind of way: <xsl:variable name="ASSERTIONS_ON" select="true()" static="true"/> <xsl:assert test="2=2" use-when="$ASSERTIONS_ON"/>
(In reply to Michael Kay from comment #1) > Note, this change means it is no longer possible to control assertion > enablement in this kind of way: > > <xsl:variable name="ASSERTIONS_ON" select="true()" static="true"/> > > <xsl:assert test="2=2" use-when="$ASSERTIONS_ON"/> Interesting. But I have always found it extremely cumbersome to have the requirement to switch assertions on/off by having to use use-when on each and every xsl:assert, which kind-of violates the whole idea behind assertions as being a light-weight simple and quick approach to asserting your code. Your code suggests the requirement or wish to be able to switch assertions on/off in the stylesheet, which, on the WG meeting was considered a non-necessity. Which brings us back to the idea of having an enable-assertions as a global attribute on xsl:stylesheet and xsl:package, with scope to the current package. I'm still somewhat silently rooting for it ;).
For reference, the proposal in comment#0 was accepted during XSLWG telcon of July 9, 2015, see https://lists.w3.org/Archives/Member/w3c-xsl-wg/2015Jul/0017.html (member only).