W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2003


From: Ashok Malhotra <ashokma@microsoft.com>
Date: Sun, 21 Sep 2003 14:55:38 -0700
Message-ID: <E5B814702B65CB4DA51644580E4853FB0AB92D25@red-msg-12.redmond.corp.microsoft.com>
To: "Kay, Michael" <Michael.Kay@softwareag.com>, <stephen.buxton@oracle.com>, <public-qt-comments@w3.org>
The WGs discussed these comments in the meeting on 9/16/2003 and decided
to remove the function fn:item-at.
This change will appear in the next version of the document.
All the best, Ashok 

From: public-qt-comments-request@w3.org
[mailto:public-qt-comments-request@w3.org] On Behalf Of Kay, Michael
Sent: Tuesday, July 01, 2003 1:44 PM
To: Stephen Buxton; public-qt-comments@w3.org

I agree and would go further.
If we are to keep item-at($x, $n) then it should have the same behavior
as $x[$n].
And if it has the same behavior, then we might as well drop it.
Michael Kay
-----Original Message-----
From: Stephen Buxton [mailto:stephen.buxton@oracle.com] 
Sent: 30 June 2003 15:28
To: public-qt-comments@w3.org
Functions and Operators, Section 15.1.6 
"If the value of $posParam is ... equal to zero (0), then an error is
raised ". 
This is inconsistent with the way the substring functions work. 
Suggest: each of the string functions should define what they do with
zero and negative values for position and length, and they should be

All the best, Ashok
Received on Sunday, 21 September 2003 17:55:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:56:49 UTC