[Bug 24308] Overriding templates can also be matching templates, but this case has no rules in the spec

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24308

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #6 from Michael Kay <mike@saxonica.com> ---
PROPOSAL

1. In the section heading of 3.6.2.5, change "named components" to
"components".

2. After the Note in this section, add: "The rules in the remainder of this
section apply to components having a <code>name</code> attribute (that is,
named components). The only element with no <code>name</code> attribute that
can appear as a child of <elcode>xsl:override</code> is an
<elcode>xsl:template</code> declaration having a <code>match</code> attribute
(that is, a template rule). The rules for overriding of template rules appear
in section 3.6.3. If an <elcode>xsl:template</elcode> element has both a
<code>name</code> and a <code>match</code> attribute, then it defines both a
named component and a template rule, and both sections apply."

3. In 6.6.2, after the description of ERR XTSE0550, add a statement that #all
and #unnamed must not be used on an xsl:template that is a child of
xsl:override.

4. Move the sentence "When a template rule specifies mode="#all" this is
interpreted as meaning all modes declared implicitly or explicitly within the
declaring package of the xsl:template element." from 3.6.3 to 6.6.2.

5. In 3.6.3, in the list of allowed values of the visibility attribute, delete
"hidden".

6. In 3.6.3, after the sentence "When a template rule specifies mode="#all"
this is interpreted as meaning all modes declared implicitly or explicitly
within the declaring package of the xsl:template element.", add: "A template
rule that is a child of xsl:override must not specify mode="#all".

7. In 6.9, add:

When xsl:apply-imports is used in a template rule that appears within an
xsl:override element, the instruction considers as candidates all template
rules declared in the used package.

When xsl:next-match is used in a template rules that appears within an
xsl:override element, the instruction considers as candidates first, all
preceding-sibling template rules, then all template rules declared in the used
package.

8. In the Note at the end of 3.6.3, change <xsl:apply-templates/> to
<xsl:apply-templates selet="."/>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 18 February 2014 20:02:41 UTC