On Thu, Oct 25, 2012 at 4:46 PM, Andrew Welch
<andrew(_dot_)j(_dot_)welch(_at_)gmail(_dot_)com> wrote:
On 25 October 2012 16:29, Ihe Onwuka <ihe(_dot_)onwuka(_at_)gmail(_dot_)com>
wrote:
I am writing an XML conversion, part of which entails bringing things
into the new namespace (from no namespace).
I have specified namespace X as my default namespace and my XPath
default namespace but all is not as expected.
I suspect it is because some elements are handled by an imported
identity template. Although this can be worked around this represents
an opportunity to get some clarification as to what the precise rules
are as relates to default namespace specfications and imported
stylesheets.
There is a gotcha with the identity template and import precedence...
the solution is to have an identity.xslt containing just the identity
template and then have that as your first import in the importing
stylesheet.
Why is that a gotcha? Sounds like the normal thing to do.
What I am really asking is given that set up will elements processed
by the imported identity respect the default namespace stipulations in
the importing stylesheet.
--~------------------------------------------------------------------
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>
--~--