[Bug 2269] Current template rule within xsl:for-each-group/xsl:fallback

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2269

           Summary: Current template rule within xsl:for-each-
                    group/xsl:fallback
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: All
               URL: http://www.w3.org/TR/2005/WD-xslt20-
                    20050915/#additional-dynamic-context
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: XSLT 2.0
        AssignedTo: mike@saxonica.com
        ReportedBy: antonl@nefedor.com
         QAContact: public-qt-comments@w3.org


The table in section "5.4.4 Additional Dynamic Context Components used by 
XSLT" specifies that the current template rule (CTR) is cleared by xsl:for-
each-group, xsl:matching-substring, xsl:non-matching-substring. It implies 
that the CTR is NOT cleared when an XSLT processor executes xsl:fallback 
children of xsl:analyze-string, however CTR is always cleared within 
xsl:fallback children of xsl:for-each-group.

Moreover, the previous row of the table specifies that the focus is set by 
xsl:analyze-string - i.e. not only within its xsl:matching-substring and 
xsl:non-matching-substring children, but also within its xsl:fallback children.

Though it may concern only XSLT 2.0 processors working in backwards-compatible 
mode, or early XSLT processors that do not implement XSLT 2.0 in full, it 
makes sense to be consistent in both cases.

The proposal is to specify that CTR is cleared by (and the focus is set 
by) "successful" execution of xsl:for-each-group, xsl:analyze-string, when no 
fallbacks performed.

If you decide this clarification is not worth it, we at least should be 
consistent in putting (xsl:analyze-string) OR (xsl:matching-substring, xsl:non-
matching-substring) in the first two rows of the table.

Received on Monday, 19 September 2005 20:07:54 UTC