On Mon, Jan 6, 2014 at 12:31 PM, Michael Kay <[email protected]> wrote:
> > On 6 Jan 2014, at 12:07, Ihe Onwuka <[email protected]> wrote: > > > Thank you. I'm not wishing to sound uncharitable or rude, but I > deliberately didn't ask for a solution because I wanted to focus on the > original question. > > > > Consider the use case in the context of someone who did not have access > to XQuery 3.0. > > > > Then you solve the problem using the clumsy grouping facilities of XQuery > 1.0, i.e. use distinct-values() to find the distinct persons, then select > the reviews for each of those distinct persons. > > There is a semantic relationship between these reviews. There are from the same person. That relationship is being obscured by the specification simply because they are in different collections. The reason they are in different collections is because they are different types of review. They might be on a different medium (tweet, vs like vs review on the site) or they could be reviews of different types of products (phones vs books for example). In both these examples a very good reason to have the reviews in different collections is that they entail different schemas. The price the specification as is makes you pay for using the collection arrangement is to lose the semantic relationship. Should it? Thats the real question that motivated my posing the use case.
_______________________________________________ [email protected] http://x-query.com/mailman/listinfo/talk
