Hear hear! (Even from DH & XML experts I have been told the data is consistent,
only to find it is not.)
One of my favorite pair of templates looks something like
<xsl:template match="node()" priority="-12">
<xsl:processing-instruction name="SBerr">If you loved me you would have
matched me! :-(</xsl:processing-instruction>
</xsl:template>
<xsl:template match="@*" priority="-12">
<xsl:attribute name="loves-me-not" select="'@'||name(.)"
namespace="http://bauman.zapto.org/debug/ns"/>
</xsl:template>
(Although typically I add some more debugging code, like putting the name of
the current node into the PI, too.)
________________________________
Others have made good suggestions wrt content. A simple first step I tend to
use is a wildcard element template (match="*") which logs anything not already
handled. It's crude but I have found there are sometimes differences between
what the client swears blind is the current schema, and the schema actually in
use :-)
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--