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 26679 - [xslt 3.0] Errors in xsl:expose and xsl:accept
Summary: [xslt 3.0] Errors in xsl:expose and xsl:accept
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Working drafts
Hardware: PC All
: 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: 2014-08-27 10:11 UTC by Michael Kay
Modified: 2014-09-04 19:24 UTC (History)
0 users

See Also:


Attachments

Description Michael Kay 2014-08-27 10:11:39 UTC
xsl:expose has

[ERR XTSE3020] It is a static error if an xsl:expose element matches no components in the containing package, unless the tokens in the names attribute are all wildcards.

and xsl:accept similarly has

[ERR XTSE3030] It is a static error if an xsl:accept element matches no components in the used package, unless the tokens in its names attribute are all wildcards.

The means that if the attribute names="a b c" is used, it's OK provided at least one of a, b, or c exists in the relevant package. This seems to make little sense. I think the rule should be that any token that isn't a wildcard is required to match the name of a component in the relevant package. The rules should be rewritten thus:

[ERR XTSE3020] It is a static error if a token in the names attribute of xsl:expose, other than a wildcard, matches no component in the containing package.

and xsl:accept similarly has

[ERR XTSE3030] It is a static error if a token in the names attribute of xsl:accept, other than a wildcard, matches no component in the used package.
Comment 1 Michael Kay 2014-09-04 19:23:56 UTC
The WG accepted the proposed change, and it has been applied to the spec.