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 29921 - [XSLT30] Abstract modes
Summary: [XSLT30] Abstract modes
Status: CLOSED WONTFIX
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 minor
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-07 00:17 UTC by Abel Braaksma
Modified: 2016-10-13 17:18 UTC (History)
0 users

See Also:


Attachments

Description Abel Braaksma 2016-10-07 00:17:31 UTC
The syntax for xsl:mode does not presently allow it to have abstract visibility, however, the syntax for xsl:accept allows us to use abstract visibility with a mode.

Also, xsl:expose has syntax that makes it possible to declare it abstract.

We do say, however, on xsl:expose:

[ERR XTSE3010] It is a static error if the explicit exposed visibility of a component is inconsistent with its declared visibility...

It puzzled me. I can see why we do not allow abstract modes, but perhaps this could be made a tad clearer, esp. in the sections on xsl:expose/xsl:accept?
Comment 1 Michael Kay 2016-10-13 14:32:29 UTC
The syntax for xsl:mode makes it clear that you can't declare a mode as abstract, and the tables in 3.5.3.1 and 3.5.3.2 make it clear (in my view) that you can't expose/accept something as abstract unless it was declared abstract in the first place.

I'm reluctant to work on the basis that we should include a rule twice because readers are more likely to spot it.

I think the rule is clear and no change is needed.
Comment 2 Abel Braaksma 2016-10-13 17:11:58 UTC
The WG agreed to close this as WONTFIX.