- From: Stephen Buxton <stephen.buxton@oracle.com>
- Date: Fri, 20 Feb 2004 18:35:22 -0800
- To: Daniela Florescu <danielaf@bea.com>
- Cc: public-qt-comments@w3.org
Dana, I'll take that as a "no" vote then, shall I ? :-) I realize this has been discussed before, and has been consistently labelled "maybe V2". But nested sequences - or at the very least, the ability to manipulate sequences of tuples - is so useful in so many cases that I think it's worth raising again, if only to get it towards the top of the list of things to consider for V2. - Steve B. Daniela Florescu wrote: > Stephen, > > I hope you realize that what you ask by this requirement > means redesigning 80% of the Data Model, XQuery, > Formal Semantics, Xpath, XSLT, and Function and Operators. > (and probably XML Schema, because they would need > to be able to talk about such a nested sequence..) > > My company would like to see XQuery 1.0 shipped > (it's been already 5 years...) > > Moreover, my constituency wouldn't like this change even > if we would have 10 more years to think about it. > XQuery and all the related standards are complex enough > and such a change would bring it beyond what can be > understood by a human being. > > > Best regards, > Dana > > > On Feb 20, 2004, at 10:20 AM, Stephen Buxton wrote: > >> >> SECTION 2: Basics >> >> The language should allow for nested sequences. Nested sequences >> (a.k.a sequences of sequences) will help in returning a set of >> related values easily. The current mechanism requires one to put >> those values inside an XML element which removes node identities, >> typing etc. >> >> Allowing nested sequence in later versions might be quite hard >> because of implicit rules governing atomization, normalization and >> concatenation of sequences. >> >> - Steve B. >> > >
Received on Friday, 20 February 2004 21:35:49 UTC