W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > January to March 2003

RE: Proposed resolution for issue "score-pseudo-property"

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 9 Jan 2003 21:55:19 +0100
To: <www-webdav-dasl@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCKEFAGCAA.julian.reschke@gmx.de>

OK,

here's the (first part) of the proposed change for DAV:score:

a) remove the current section about DAV:score

b) to the section about DAV:contains, add:

---
5.14.1  Result scoring (DAV:score element)

Servers SHOULD indicate scores for the DAV:contains condition by adding a
DAV:score XML element to the DAV:response element. It's value is defined
only in the context of a particular query result. The value is a string
representing the score, an integer from zero to 10000 inclusive, where a
higher value indicates a higher score (e.g. more relevant).

Modified DTD fragment for DAV:propstat:

<!ELEMENT response (href, ((href*, status)|(propstat+)),
                    responsedescription?, score?) >
<!ELEMENT score    (#PCDATA) >

Clients should note that, in general, it is not meaningful to compare the
numeric values of scores from two different query results unless both were
executed by the same underlying search system on the same collection of
resources.
---

I'll approach the DAV:nresults vs. DAV:order-by issue separately.

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

> -----Original Message-----
> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Elias
> Sent: Saturday, November 30, 2002 8:44 PM
> To: www-webdav-dasl@w3.org
> Subject: Re: Proposed resolution for issue "score-pseudo-property"
>
>
>
> 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 Thursday, 9 January 2003 15:56:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:09 GMT