- From: Elias <elias@cse.ucsc.edu>
- Date: Sat, 30 Nov 2002 11:44:16 -0800
- To: www-webdav-dasl@w3.org
Agreed. Whereas I can contrive a use case for ordering by lowest score first, it doesn't strike me as a particularly 'must have' feature. The most common case will be people looking for specific content. Elias Lisa Dusseault wrote: > That sounds like the right thing to do. Ordering by lowest score first > seems such a low-priority feature that if somebody turns out to need it > someday they can add an extension for that. > > lisa > > >>-----Original Message----- >>From: Julian Reschke [mailto:julian.reschke@gmx.de] >>Sent: Saturday, November 30, 2002 12:41 AM >>To: www-webdav-dasl@w3.org >>Subject: RE: Proposed resolution for issue "score-pseudo-property" <Prior comment removed> >> >>Thinking about it, the relationship *really* is between DAV:nresults > and the >>presence of DAV:score -- not the fact that the client requests > ordering by >>DAV:score. Is there a use case for combining DAV:nresults with > ordering by >>DAV:score in *ascending* order (lowest scores first)? >>If not, we can just point out that combining any operator that > produces >>scores (right now thats DAV:contains) with DAV:results should cause >>the server to return the "n" top scoring results. >> >>-- >><green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Saturday, 30 November 2002 14:50:15 UTC