This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: XML Schema/XSL conflict (can't differentiate unqualified locals)?
- To: xsl-list at lists dot mulberrytech dot com
- Subject: Re: [xsl] XML Schema/XSL conflict (can't differentiate unqualified locals)?
- From: David Carlisle <davidc at nag dot co dot uk>
- Date: Thu, 11 Oct 2001 09:20:58 +0100
- References: <000d01c1517c$1ce74e40$074c3c3e@PCUKMKA> <m3bsjf2sa9.fsf@colina.demon.co.uk>
- Reply-To: xsl-list at lists dot mulberrytech dot com
>>>>> "Michael" == Michael Kay <mhkay@iclway.co.uk> writes:
Michael> You can say xmlns="" to cancel the default namespace
Michael> declaration, but you can't do xmlns:xyz="" to cancel a
Michael> non-default namespace declaration.
Ah - now I can see it in the recommendation - I had overlooked that - thanks.
Although this isn't as arbitrary as it might seem. While xmlns="" is
described as cancelling the default declaration, another way to look at
it (which is essentially the way XPath looks at it) is to say that it
binds the null prefix to the null namespace. After that <x/> isn't an
error it just denotes x in no namespace.
Conversely if xmlns:x="" were allowed to unbind the prefix x:x then
<x:x/> would go from being namespace well formed to being a namespace
error.
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