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 29919 - [XSLT30] Effect of use-when on xsl:package
Summary: [XSLT30] Effect of use-when on xsl:package
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Candidate Recommendation
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: 2016-10-06 22:43 UTC by Abel Braaksma
Modified: 2016-10-13 19:51 UTC (History)
0 users

See Also:


Attachments

Description Abel Braaksma 2016-10-06 22:43:36 UTC
In section 3.13.1 Conditional Element Inclusion we mention the following about its use on xsl:stylesheet and xsl:transform:

"If the xsl:stylesheet or xsl:transform element itself is effectively excluded, the effect is to exclude all the children of the xsl:stylesheet or xsl:transform element, but not the xsl:stylesheet or xsl:transform element or its attributes."

It seems to make sense to include xsl:package here as well. I don't necessarily see a use-case for it (but I don't see one for xsl:stylesheet/xsl:transform either), but neither do I see how otherwise a package is supposed to behave if use-when="false()" on xsl:package.
Comment 1 Michael Kay 2016-10-13 15:00:33 UTC
I agree.

(I don't think there was ever a particularly strong use case for this. We either had to give it a meaning, or make it an error, and we chose to give it a meaning.)
Comment 2 Michael Kay 2016-10-13 19:51:36 UTC
The WG agreed and the change has been applied.