But the two proposals of Florent and Vladimir are basically the
literal example one more time where xsl:namespace is not needed unless
in a dynamic solution as in my alternative 3. We could make Vladimir's
dynamic but it will not make it less artificial or confusing than my
own example. Instead of the xsi namespace we will get some other
namespace.
Can you please clarify on how to eliminate xsl:namespace in the example I've
provided?
<xsl:param name="value" as="xs:QName"/>
<element value="{$value}">
<xsl:namespace
name="{prefix-from-QName($value)}"
select="{namespace-uri-from-QName($value)}/>
...
</element>
--
Vladimir Nesterovsky
http://www.nesterovsky-bros.com/
--~------------------------------------------------------------------
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>
--~--