- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 19 Sep 2005 17:10:05 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2268 Summary: xsl:apply-imports errors XTDE0560 and XTDE0565 seem to be duplicates Product: XPath / XQuery / XSLT Version: Last Call drafts Platform: All 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 A clarification is needed for errors XTDE0560 and XTDE0565. Section 6.7 contains the following note: //These rules ensure that when xsl:apply-imports or xsl:next-match is called, the context item is the same as when the current template rule was invoked, and is always a node.// I think this note should mention one additional constraint "and the current template rule is not null". Now let us consider two different dynamic errors described in this section: //[ERR XTDE0560] It is a non-recoverable dynamic error if xsl:apply-imports or xsl:next-match is evaluated when the current template rule is null. [ERR XTDE0565] It is a non-recoverable dynamic error if xsl:apply-imports or xsl:next-match is evaluated when there is no context item or when the context item is not a node.// Taking into account the note above, these two errors seem to be identical: if CTR is not null, then the context item is guaranteed to exist and be a node.
Received on Monday, 19 September 2005 17:11:46 UTC