On 05/05/2008, Michael Kay <mike(_at_)saxonica(_dot_)com> wrote:
The "xs" namespace is a bit odd in that it's known to
> processors, like the "xsl" namespace, but unlike the xsl
> namespace it makes it into the result tree and requires pruning.
The reason for this: if the "xs" namespace had been excluded by default, we
would have had do something special for users who want to generate something
like <d xsi:type="xs:date"/>.
If it was excluded by default, could you not override that by
explicitly declaring it - for example on the output root element? But
then you'd need to declare it twice if you really wanted it in the
output...
Or perhaps use namespace-alias, just like when you really need the xsl
namespace in the output.
Either way not great, but maybe preferable to have to work a bit
harder in the special case, rather then every time for every
transform.
--
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/
--~------------------------------------------------------------------
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>
--~--