Re: [xquery-talk] Collections - family relationships

2014-01-05 Thread David Lee
Docs don't even need uri's. ... That's where the fun really starts in info space Sent from my iPad (excuse the terseness) David A Lee d...@calldei.com > On Jan 5, 2014, at 9:16 PM, "Liam R E Quin" wrote: > >> On Sun, 2014-01-05 at 22:23 +, David Lee wrote: >> Seems there is no guarantee t

Re: [xquery-talk] Collections - family relationships

2014-01-05 Thread Liam R E Quin
On Sun, 2014-01-05 at 22:23 +, David Lee wrote: > Seems there is no guarantee that >uri-collection()!doc(.) produces the same results as collection() Right - collection() really marks the border of what we (W3C) could standardize at the time, when many implementations of XQuery do not (f

Re: [xquery-talk] Collections - family relationships

2014-01-05 Thread David Lee
Re: fn:uri-collection() !! Another new function for me ... looks useful If/and/only/if it correlates to what you want ... Seems there is no guarantee that uri-collection()!doc(.) produces the same results as collection() this is a broad field, that incidentally I think is underappreciated.

Re: [xquery-talk] Collections - family relationships

2014-01-05 Thread David Lee
Thanks. Not even knowing of the existence of fn:filter or fn:for-each-pair I wrote just now my version in old-fashioned-xquery declare function common:node-index-of( $nodes as node()* , $node as node() ) as xs:integer ? { for $n at $pos in $nodes return if( $n is $node )

Re: [xquery-talk] Collections - family relationships

2014-01-05 Thread Andrew Welch
On 5 January 2014 21:20, Michael Kay wrote: > > On 5 Jan 2014, at 20:59, David Lee wrote: > >> Given those truths ... >> If you do have a sequence from fn:collection() or another function you *can* >> find the position of a document in that collection and its 'sibling' >> >> Note: this may be a

Re: [xquery-talk] Collections - family relationships

2014-01-05 Thread Michael Kay
On 5 Jan 2014, at 21:24, David Lee wrote: > Arg ... so your saying index-of causes a string atomization ? > Ug. I know it wants item* and uses "eq" as the comparison but didn't > realize that would stringify documents ... Actually the function signature for index-of expects xs:anyAtomicType

Re: [xquery-talk] Collections - family relationships

2014-01-05 Thread David Lee
Arg ... so your saying index-of causes a string atomization ? Ug. I know it wants item* and uses "eq" as the comparison but didn't realize that would stringify documents ... Do you know of a sequence function that uses document or node ID's ? David

Re: [xquery-talk] Collections - family relationships

2014-01-05 Thread Michael Kay
On 5 Jan 2014, at 20:59, David Lee wrote: > Given those truths ... > If you do have a sequence from fn:collection() or another function you *can* > find the position of a document in that collection and its 'sibling' > > Note: this may be a horribly inefficient thing to do so buyer beware

Re: [xquery-talk] Collections - family relationships

2014-01-05 Thread David Lee
Given those truths ... If you do have a sequence from fn:collection() or another function you *can* find the position of a document in that collection and its 'sibling' Note: this may be a horribly inefficient thing to do so buyer beware let $c := fn:collection(), $doc := local:pick-a

Re: [xquery-talk] Collections - family relationships

2014-01-05 Thread Michael Kay
On 5 Jan 2014, at 16:50, Ihe Onwuka wrote: > If x is the document element of a document in a collection, is it the sibling > of y that is the document element of another document in the same collection? No. > > If not why not? "Why" questions are very difficult to answer. Do you want a histo

Re: [xquery-talk] Collections - family relationships

2014-01-05 Thread G. Ken Holman
At 2014-01-05 16:50 +, Ihe Onwuka wrote: If x is the document element of a document in a collection, is it the sibling of y that is the document element of another document in the same collection? If not why not? It doesn't, because the specification says it doesn't: http://www.w3.org

Re: [xquery-talk] Collections - family relationships

2014-01-05 Thread Joe Wicentowski
XPath axes only operate within the bounds of a single document. On Sun, Jan 5, 2014 at 11:38 AM, Ihe Onwuka wrote: > Certainly in the XPath sense and why not in the general sense (whatever that > means). > > > On Sun, Jan 5, 2014 at 5:36 PM, Joe Wicentowski wrote: >> >> Do you mean "sibling" in

Re: [xquery-talk] Collections - family relationships

2014-01-05 Thread Ihe Onwuka
Certainly in the XPath sense and why not in the general sense (whatever that means). On Sun, Jan 5, 2014 at 5:36 PM, Joe Wicentowski wrote: > Do you mean "sibling" in the sense of the XPath axes preceding-sibling > and following-sibling, or in the general sense of documents being > "children" o

Re: [xquery-talk] Collections - family relationships

2014-01-05 Thread Joe Wicentowski
Do you mean "sibling" in the sense of the XPath axes preceding-sibling and following-sibling, or in the general sense of documents being "children" of a "parent" collection and thus "siblings"? On Sun, Jan 5, 2014 at 10:50 AM, Ihe Onwuka wrote: > If x is the document element of a document in a co

[xquery-talk] Collections - family relationships

2014-01-05 Thread Ihe Onwuka
If x is the document element of a document in a collection, is it the sibling of y that is the document element of another document in the same collection? If not why not? ___ talk@x-query.com http://x-query.com/mailman/listinfo/talk