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 23325 - [XSLT 3.0] Interaction of the "initial" and "visibility" attributes of xsl:mode
Summary: [XSLT 3.0] Interaction of the "initial" and "visibility" attributes of xsl:mode
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: 2013-09-23 09:08 UTC by Michael Kay
Modified: 2014-05-15 14:00 UTC (History)
0 users

See Also:

Attachments

Description Michael Kay 2013-09-23 09:08:51 UTC 
xsl:mode has two attributes e.g. initial="yes", visibility="private". We don't specify how these interact.

I wonder whether initial=yes!no is needed; can't we say that any mode that is public in the top-level package is eligible to be used as the initial mode, and any mode that is not public in the top-level package is not eligible?
Comment 1 Michael Kay 2013-09-25 15:47:31 UTC 
We noted that if someone tries to specify visibility=public and initial=no on a mode, then an application could get around this restriction by creating a trivial package containing an apply-templates instruction in that mode. So we think the "initial" attribute is pointless.

There may be some documentary value, but this can equally be achieved using visibility="public".

Agreed that it makes little sense.
Comment 2 Michael Kay 2013-09-25 15:49:24 UTC 
We further noted that initial=yes|no was added to the spec before we introduced packages and visibility.
Comment 3 Michael Kay 2013-09-26 07:13:45 UTC 
Change now applied to the spec.