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 24548 - Vague wording about suppressing errors in global variables when priming a stylesheet
Summary: Vague wording about suppressing errors in global variables when priming a sty...
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 trivial
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: 2014-02-06 00:11 UTC by Abel Braaksma
Modified: 2014-02-16 19:51 UTC (History)
1 user (show)

See Also:


Attachments

Description Abel Braaksma 2014-02-06 00:11:01 UTC
Under 2.3.2 Priming a Stylesheet (http://www.w3.org/TR/xslt-30/#priming-stylesheet), the second paragraph under the second bullet point, the text reads (about initial context items and errors during priming):

"The error can be suppressed by use of xsl:try and xsl:catch within the initialization of the variable or parameter."

I think it is the reverse: it can be suppressed when the initialization code is wrapped inside an xsl:try and xsl:catch block.
Comment 1 C. M. Sperberg-McQueen 2014-02-13 09:13:00 UTC
We discussed this in Prague and concluded that the existence of the issue report demonstrates that the text is susceptible to misinterpretation; editor to recast.
Comment 2 Michael Kay 2014-02-16 19:51:45 UTC
The text has been changed to read:

The error can be suppressed by use of <elcode>xsl:try</elcode> and <elcode>xsl:catch</elcode> within the sequence constructor used to initialize the variable or parameter. (It cannot be suppressed by use of <elcode>xsl:try</elcode> around a reference to the global variable.)