Thanks for your response

What I don't understand is why XMLSpy">XMLSpy can make them "two completely
different documents" by simply verifing a message against a XSD.
I tried the local-name() method but it didn't work, the mapping appeared to
return a match, but then none of the data that is scanned within the
template returns valid branches...

Oh, it's so confuzzling. **8-$

Thanks again
Dan.

"Oleg Tkachenko [MVP]" <oleg@NO!SPAM!PLEASEtkachenko.com> wrote in message
news:e%23yHDVEAEHA.916@t......
Daniel Bass wrote:

> message before XMLSpy">XMLSpy'd.
>
> < Abc >
>      < SubInnerDef >
>           < InnerGhi value="Test" />
>      < SubIinnerDef >
> </Abc>
>
>
>
> message after XSD was added via XMLSpy">XMLSpy
>
> < Abc
>           xmlns="http://www.wbf.org/xml/b2mml-v02"

These are two completely different documents. Namespace is like second
name, these two Abc elements have nothing but local name part in common.

> the second XML snippet fails in the <xsl:template match='Abc'> because of
> the namespace and other "attributes".
>
> Is there a way to write the XSL so that it work for both cases?
Yes, but that's poor solution.
You can use namespace-unaware name tests:

<xsl:template match="*[local-name()='Abc']">

-- 
Oleg Tkachenko [XML MVP, XmlInsider]
http://blog.tkachenko.com