- From: <bugzilla@jessica.w3.org>
- Date: Thu, 19 Mar 2015 12:48:54 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28240 Bug ID: 28240 Summary: [XSLT30] conflicting text in the section on default modes and suggestion to allow #current Product: XPath / XQuery / XSLT Version: Member-only Editors Drafts Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P2 Component: XSLT 3.0 Assignee: mike@saxonica.com Reporter: abel.braaksma@xs4all.nl QA Contact: public-qt-comments@w3.org The introduction text on default modes (3.8.2 The [xsl:]default-mode Attribute) contains a conflicting statement, in the introduction, the value #default is allowed, but then the text says in the second para: <quote> The value MUST either be an EQName, or the token #unnamed which refers to the unnamed mode. It is not necessary for the referenced mode to be explicitly declared in an xsl:mode declaration. </quote> In other words, the "must" in this sentence seems to remove the ability to use #default as mode name. Also, I think it will make sense to extend the above sentence with something like "[...], regardless of the setting of xsl:package/@declared-modes". In addition, I was wondering if it makes sense to allow #current, which will have the same meaning as using <xsl:apply-templates mode="#current"/> and is a shortcut for a common programming style where inside an xsl:template, one typically wants to stay within the current mode, unless you specify otherwise. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 19 March 2015 12:48:55 UTC