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 29095 - [xslt 3.0] Edge case inconsistency between xsl:expose and xsl:accept
Summary: [xslt 3.0] Edge case inconsistency between xsl:expose and xsl:accept
Status: CLOSED WORKSFORME
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Last Call 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: 2015-08-28 11:53 UTC by Michael Kay
Modified: 2015-10-29 12:42 UTC (History)
0 users

See Also:

Attachments

Description Michael Kay 2015-08-28 11:53:46 UTC 
For both xsl:expose and xsl:accept, we allow multiple explicit references to the same component, e.g.

<xsl:expose component="variable" names="v1 v2" visibility="private"/>
<xsl:expose component="variable" names="v2" visibility="private"/>

and ignore all but the last.

However, a careful reading suggests that xsl:accept validates the visibility of all the declarations, whereas xsl:expose only validates the one that is actually used.

I think that we should validate them all, in both cases.
Comment 1 Michael Kay 2015-10-15 15:23:49 UTC 
I am unable to reconstruct the reasoning that led to the raising of this bug report, so I am withdrawing it.