Because there might be an element
<doc xmlns:foo="...">
far up the hierarchy.
xmlns:foo="..." will be suppressed there by exclude-result-prefixes="#all".
Keeping xmlns:foo up there prevents the declaration to occur repeatedly
at any descendant
<foo:p> (which will otherwise be <foo:p xmlns:foo="...">, and this will
really make your document verbose).
On 2011-12-05 13:39, Andrew Welch wrote:
Hi all,
Does anyone have a reason why:
exclude-result-prefixes="#all"
shouldn't be considered boilerplate?
thanks
--
Gerrit Imsieke
Geschäftsführer / Managing Director
le-tex publishing services GmbH
Weissenfelser Str. 84, 04229 Leipzig, Germany
Phone +49 341 355356 110, Fax +49 341 355356 510
gerrit(_dot_)imsieke(_at_)le-tex(_dot_)de, http://www.le-tex.de
Registergericht / Commercial Register: Amtsgericht Leipzig
Registernummer / Registration Number: HRB 24930
Geschäftsführer: Gerrit Imsieke, Svea Jelonek,
Thomas Schmidt, Dr. Reinhard Vöckler
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--