[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: To namespace or not to Namespace ....

• From: Andrew Welch <andrew.j.welch@gmail.com>
• To: David Carlisle <davidc@nag.co.uk>
• Date: Fri, 9 Apr 2010 10:05:56 +0100

On 9 April 2010 09:42, David Carlisle <davidc@nag.co.uk> wrote:
> On 09/04/2010 01:07, Liam R E Quin wrote:
>>
>> You can't write, for example, /html/head/meta[@name eq 'link'] but,
>> instead, /h:html/h:head/h:meta[@name eq 'link'],
>
>
> well actually you can since you've used eq you are presumably using xpath2
> so you can set the default element namespace to be xhtml
> (unfortunately Xquery messed this up and combined the notion of default
> namespace in the result and default namespace in the query, so if that
> fragment was xquery rather than xpath then you can only do that if you are
> generating xhtml as well as querying it)

XQuery really messed this up big time... such a simple thing, and such
a huge amount of hassle caused by it.  I know I'm not the only one to
be amazed when you first realise that is what is happening.




-- 
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

• Follow-Ups:
  • RE: To namespace or not to Namespace ....
    • From: "Michael Kay" <mike@saxonica.com>

• References:
  • To namespace or not to Namespace ....
    • From: David <dlee@calldei.com>
  • Re: To namespace or not to Namespace ....
    • From: Kendall Shaw <kshaw@kendallshaw.com>
  • Re: To namespace or not to Namespace ....
    • From: Liam R E Quin <liam@w3.org>
  • Re: To namespace or not to Namespace ....
    • From: David Carlisle <davidc@nag.co.uk>