DT said:
3) You do not want the transformation to break each time an
error condition is met, it is waste of time. Instead, you
want as many reports about failed assertions as feasible
during one run. Embedding back-references to the code of
the stylesheet and to the input tree into the
transformation result and using a tool to check and report
assertion failures (not just validity assertion, and
obviously not just vcalidity assertions using one schema
language) is much better for the following reasons:
- it is as powerful fo the same validation task
- its is more powerful for debuggin in general since it allows
to provide other types of assertions too, using
Schematron, for example;
- it is easier to implement and support
- it provides clear separation of layers
- it does not contaminate the language with ugly kludges solving
partial problems.
<xsl:variable name="debug" select="true()"/>
<xsl:template match="complicatedXPATHExpression">
<xsl:if test="$debug">
complicatedXPATHExpression template:
src: <xsl:value-of select="name(..)"/>/<xsl:value-of select="name()"/>
val: [<xsl:value-of select="."/>]
</xsl:if>
normal template processing
I like that.
I'm often surprised by which template is producing content.
If going to html,
wrap it in html to make it stand out.
regards DaveP
-
DISCLAIMER:
NOTICE: The information contained in this email and any attachments is
confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of the
content of it or of any attachment; you are requested to notify the
sender immediately of your receipt of the email and then to delete it
and any attachments from your system.
RNIB endeavours to ensure that emails and any attachments generated by
its staff are free from viruses or other contaminants. However, it
cannot accept any responsibility for any such which are transmitted.
We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email and
any attachments are those of the author and do not necessarily represent
those of RNIB.
RNIB Registered Charity Number: 226227
Website: http://www.rnib.org.uk
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list