XSL processor limitation?

[Mark Norman <mn...@cup.hp.com>]

I am trying to create a new row in an HTML table
after the 3rd element. When I reach the fourth
element, I am inserting HTML tags to end the
previous row and start the next one. My XSL
code fragment looks like this:


 <xsl:template match="book[4]">
  <xsl:value-of select="@title"/>
  </tr>
  <tr>
 </xsl:template>

The resulting HTML will conform to the rules
of matching begin and end tags, but the XSL
processor is validating my XSL code not on the
results it will produce, but on the pre-processed
version. So, it thinks that having the </tr> tag
before the </xsl:template> tag is an error.

This seems like a serious limitation. I already
have ways to work around this, but I am interested
in addressing the basic problem: can I tell
the XSL processor to validate only my XSL statements
and not the HTML?


thanks,

Mark Norman