[xquery-talk] effect of namespace on collection function; weird

[David Lee]

In hindsight, that's too bad  :(
In most of the cases where I work with XML with namespaces, I'm generating 
in a different namespaces (or none) then I am querying.
My own experience would suggest that's the common, not the outlying case.


----------------------------------------------------
David A. Lee
dlee at calldei.com
http://www.calldei.com
http://www.xmlsh.org


--------------------------------------------------
From: "Michael Rys" <mrys at microsoft.com>
Sent: Tuesday, February 02, 2010 4:10 PM
To: "Michael Kay" <mike at saxonica.com>; "'James Fuller'" 
<james.fuller.2007 at gmail.com>; "'Elliotte Rusty Harold'" 
<elharo at ibiblio.org>
Cc: <talk at x-query.com>
Subject: RE: [xquery-talk] effect of namespace on collection function; weird

> I remember having this raised as a usability issue but we decided at the 
> time that we do not want to keep track of two default element namespaces 
> :(.
>
> Best regards
> Michael
>
> -----Original Message-----
> From: talk-bounces at x-query.com [mailto:talk-bounces at x-query.com] On Behalf 
> Of Michael Kay
> Sent: Tuesday, February 02, 2010 7:00 AM
> To: 'James Fuller'; 'Elliotte Rusty Harold'
> Cc: talk at x-query.com
> Subject: RE: [xquery-talk] effect of namespace on collection function; 
> weird
>
>
>> yes frustrating, but dont forget you can use:
>>
>> declare default element namespace "http://www.w3.org/1999/xhtml";
>>
>> to change the default element namespace in XQuery
>>
>
> But it still changes the default both for constructing new elements and 
> for accessing existing ones. What the user wants here is different 
> defaults for the two cases.
>
> Regards,
>
> Michael Kay
> http://www.saxonica.com/
> http://twitter.com/michaelhkay
>
>
> _______________________________________________
> talk at x-query.com
> http://x-query.com/mailman/listinfo/talk
>
>
> _______________________________________________
> talk at x-query.com
> http://x-query.com/mailman/listinfo/talk
>