Re: Schema-aware validation of XHTML result-document
> Its certainly raised an interesting question - should the serialised > version of the validated result be the per or post validation > instance? reading the spec I think Michael's right that it has to be the post validation instance, however it's not often useful to default these values on the way out (since if they were not there, the consuming application would anyway default them back when it (re)validated, I think you can do <xsl:result-document href="nodefaults.xml"> <xsl:variable name="x"> <xsl:apply-templates/> </xsl:variable> <xsl:variable name="x-valid"> <xsl:copy-of select="$x" validation="strict"/> </xsl:variable> <xsl:if test="$x-valid"> <xsl:sequence select="$x"/> </xsl:if> </xsl:result-document> which builds an unvalidated tree, then builds a validated tree (which will generate the necessary error and debugging info if the result is not valid) then outputs the original tree. Or of course more simply just use a locally modified schema (I've often removed these defaults from html dtd over the years, and would no doubt remove them from the xhtml schema if I found myself using that) David
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format