Subject: Re: [xsl] xsl/xslt coding standard From: Jeni Tennison <jeni@xxxxxxxxxxxxxxxx> Date: Fri, 16 Aug 2002 08:23:52 +0100 |
Hi Steve, > For the XSLT Standard Library, which is all about establishing > engineering standards for XSLT stylesheets, I adapted Norm Walsh's > DocBook-in-XSLT approach. It seems to work just fine, and I haven't > observed any problems requiring xsl:fallback. I think that's probably because you put all the documentation at the top level of the stylesheet. If you tried to include it within a template then you would either get the documentation added to the result or get an error (if you asserted the documentation namespace was a namespace for extension elements). > If exclude-result-prefixes works OK, why introduce something new? exclude-result-prefixes doesn't work OK, or at least it doesn't work OK if (a) you want to put documentation *within* templates and (b) you don't want to have to nest it inside an instruction that guarantees it won't be processed [such as an xsl:if test="false()" or an xsl:for-each select="/.."]. Cheers, Jeni --- Jeni Tennison http://www.jenitennison.com/ XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] xsl/xslt coding standard, Steve Ball | Thread | Re: [xsl] xsl/xslt coding standard, Brian Grainger |
Re: Re: [xsl] any good solution for, stoneson | Date | Re: [xsl] Re: xsl/xslt coding stand, Jeni Tennison |
Month |