Thanks Tom.  Suppose that I do want Saxon to carry the namespace
declaration from the stylesheet over to the result document.  How do I
do it?  /Roger

"Passin, Tom" wrote:
> 
> Both Xalan and Saxon are correct.  True, the Xalan output declares an
> extra namespace, but the FitnessCenter element does not belong to that
> namespace. So the presence of the declaration has no effect on the
> interpretation of the document.
> 
> Cheers,
> 
> Tom P
> 
> [Roger L. Costello]
> 
> > I have observed a difference in behavior of Xalan and Saxon with
> > namespaces.  Consider this stylesheet:
> >
> > <?xml version="1.0"?>
> > <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> >                 xmlns:fit="http://www.keeping-fit.org"
> >                 version="1.0">
> >
> >     <xsl:output method="xml"/>
> >
> >     ...
> >
> > </xsl:stylesheet>
> >
> > Note the namespace declaration in the stylesheet:
> >
> >     xmlns:fit="http://www.keeping-fit.org"
> >
> > When I run Xalan I get this output:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <FitnessCenter xmlns:fit="http://www.keeping-fit.org">
> >     ...
> > </FitnessCenter>
> >
> > Observe that the namespace declaration from the stylesheet has been
> > carried over to the result document.
> >
> > Now, here is the output from running Saxon:
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <FitnessCenter>
> >     ...
> > </FitnessCenter>
> >
> > Notice that the namespace declaration from the stylesheet was NOT
> > carried over to the result document.
> >
> > Which is correct - Xalan or Saxon?  /Roger
> >
> >
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


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