This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: exclude-result-prefixes



> and while I thought
> exclude-result-prefixes was supposed to handle this,

e-r-p only causes namespace declarations that are not used to be
excluded. If you output any element or attribute node in a namespace
then the system will always output a suitable declaration for that
namespace. 

   <xsd:element name="{@name}" 

this is generatimg an element node in the xsd namespace. So th esystem
has to ensure that there is a namespace declaration in scope for xsd:
otherwise the output wouldn't be namespace conformant.

If your objection is that you are getting too many namespace
declarations, then perhaps you have ommited to put the parent (schema?) 
element into the correct namespace. Most systems don't output namespace
declarations that are already present on an ancestor.

David

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]