On Wed, Jan 8, 2014 at 11:03 AM, David Carlisle <[email protected]> wrote:
> On 08/01/2014 09:35, Ihe Onwuka wrote:
>
> >
>> > <person>{$thing/@name}</person>
>>
>>
> I can't begin to fathom the rationale for the exception or the value of
>> such an exception over the simple rule of atomizing sequences if they
>> appear in contexts where a value is expected.
>>
>
> why do you think an atomised value is expected here?
because the value you put in an attribute must be atomic.......
> would you expect element nodes
>
>
> <person>{$thing/name}</person>
>
> to be atomised as well? (They aren't: this would add a sequence of <name>
> children to <person>)
>
......and the value of an element doesn't have to be.
>
>
> > It seems to me that it is
>
>> just demanding the explicit call of the data function (which is exactly
>> what I put in) for something it could just have easily handled implicitly.
>>
>>
> But this construct is designed to add attribute nodes, so implicit
> atomization would be undesirable.
Why? It cannot be a placeholder for anything but an atomic value.
>
>
_______________________________________________
[email protected]
http://x-query.com/mailman/listinfo/talk
