RE: Carrying Namespaces through a XSL to XSL Transform

> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Evan Lenz
> Sent: Friday, December 29, 2000 5:31 AM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE:  Carrying Namespaces through a XSL to XSL
> Transformation
>
>
> I agree that disable-output-escaping should not be used in this case.  The
> only defensible use of disable-output-escaping that I remember
> seeing is the
> rendering of non-well-formed HTML in a browser (where the HTML markup is
> actually content, not markup).
>
> But there still is a problem here.  Namespace nodes found only in
> the source
> tree are only copied to the result tree when nodes from the
> source tree are
> copied.  If the stylesheet you're generating doesn't copy those nodes from
> the source tree, the namespace nodes won't be copied either.  (When
> namespace nodes are copied, you apparently can trust the
> resulting declared
> prefixes to be the same as that of the source --
> http://www.biglist.com/lists/xsl-list/archives/200010/msg00206.html)

Thanks for the lengthy explanation.

If I understand correctly, this is basically caused by the fact that, in the
desired generated XSLT, the namespace declaration is only required because
the prefix appears in XPath expressions, but not in a literal result
element.

Seems to me that this is a hole that should be closed in XSLT 1.1... (or is
it?).

Julian


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list