- From: Kay, Michael <Michael.Kay@softwareag.com>
- Date: Tue, 12 Aug 2003 17:13:05 +0200
- To: Ashok Malhotra <ashokma@microsoft.com>, Michael Rys <mrys@microsoft.com>, public-qt-comments@w3.org
Received on Tuesday, 12 August 2003 11:13:44 UTC
> Michael: > As you may remember we discussed the removal of this function > at the F&O meeting in Redmond on 7/18 and the F&O taskforce > decided not to recommend its removal. Was any decision made to align the semantics of item-at($s, $p) with $s[$p], so that implementations can use the same underlying code? At present item-at() fails if $p is out of range, whereas $s[$p] returns (). Michael Kay > > All the best, Ashok > > > -----Original Message----- > > From: public-qt-comments-request@w3.org [mailto:public-qt-comments- > > request@w3.org] On Behalf Of Michael Rys > > Sent: Tuesday, July 01, 2003 11:58 AM > > To: public-qt-comments@w3.org > > Subject: MS-FO-LC1-093: fn:item-at > > > > > > Class: Editorial > > > > Section 15.1.6: We already have the [] notation for indexing > sequences. > > This function is not needed except for defining the semantics of > > [position()=x] (at most). In that case, move this into the formal > > semantics as a function belonging to fs: pseudo-namespace. > > > >
Received on Tuesday, 12 August 2003 11:13:44 UTC