- From: <bugzilla@jessica.w3.org>
- Date: Mon, 19 Oct 2015 09:14:59 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29209 Bug ID: 29209 Summary: [xslt30] Template rules within xsl:override Product: XPath / XQuery / XSLT Version: Last Call drafts Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: XSLT 3.0 Assignee: mike@saxonica.com Reporter: mike@saxonica.com QA Contact: public-qt-comments@w3.org Target Milestone: --- The last paragraph in 6.1 is clearly wrong: If the parent of the xsl:template element is an xsl:override element, then there must be a name attribute and no match attribute, and the package that is the target of the containing xsl:use-package element must contain among its components a named template whose symbolic identifier is the same as this named template, and which has a compatible signature. because it does not allow adding template rules to a mode accepted from the used package. I think it should read: If the parent of the xsl:template element is an xsl:override element, then one of the following conditions must be true: 1. there must be a name attribute and no match attribute, and the package identified by the containing xsl:use-package element must contain among its components a named template whose symbolic identifier is the same as this named template, and which has a compatible signature. 2. there is a match attribute and a mode attribute, and no name attribute; the mode attribute must contain a single token which is the name of a mode that is exposed, with visibility equal to *public*, by the package identified by the containing xsl:use-package element. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 19 October 2015 09:15:04 UTC