Sort doesn't make any sense in the first case, and should be accompanied by
a request for records in the second case.
Ralph
> -----Original Message-----
> From: Ray Denenberg [mailto:[log in to unmask]]
> Sent: Friday, June 21, 2002 9:54 AM
> To: [log in to unmask]
> Subject: Re: sort parameter
>
>
> There might not be a record schema id included in the request
> (if zero records
> are requested, or if this is a request to sort an existing
> result set).
> --Ray
>
> "LeVan,Ralph" wrote:
>
> > I don't want the tagpath to come from a different schema
> than the one
> > already requested for the record. I want the users to see
> that the records
> > were sorted by fields in those records. So the schema
> attribute on the
> > elementPath element is unnecessary.
> >
> > Ralph
> >
> > > -----Original Message-----
> > > From: Ray Denenberg [mailto:[log in to unmask]]
> > > Sent: Friday, June 21, 2002 9:44 AM
> > > To: [log in to unmask]
> > > Subject: sort parameter
> > >
> > >
> > > A Sort parameter, might look something like this:
> > >
> > > -----------------
> > > <sort>
> > > <sortKey direction="ascending">
> > > <index>bathTitleWord</index></sortKey>
> > > <sortKey direction="ascending">
> > > <elementPath schema= "schema identifier">
> > > <element> element1</element>
> > > <element> element2</element>
> > > ....
> > > </elementPath>
> > > </sortKey>
> > > <sortKey direction="ascending"> <sortKeyName> title
> > > <sortKeyName></sortKey>
> > > </sort>
> > > ---------------------
> > >
> > > That gives three options: index (Rob), element path (Ralph),
> > > or sort key name
> > > (Alan).
> > >
> > > Do we need all three or can we agree on one?
> > >
> > > --Ray
> > >
>
|