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: Mon, 13 Jan 2003 16:47:52 +0100
To: <www-webdav-dasl@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCOEMAGCAA.julian.reschke@gmx.de>

Hi.

I note that the solution that's currently in (see below) does not take into
account the theoretical case where ordering by DAV:score is to be combined
with ordering by a specific property value. In the previous dratft, one
could have used:

<d:orderby>
  <d:order>
    <d:prop><d:score/></d:prop>
    <d:ascending/>
  </d:order>
  <d:order>
    <d:prop><d:getcontentlength/></d:prop>
    <d:descending/>
  </d:order>
</d:orderby>

...which isn't possible anymore.

If this is a problem, we can use the following format instead:

<d:orderby>
  <d:order>
    <d:score/>
    <d:ascending/>
  </d:order>
  <d:order>
    <d:prop><d:getcontentlength/></d:prop>
    <d:descending/>
  </d:order>
</d:orderby>

So do we need the ability to sort by score *and* other properties at the
same time? I honestly can't tell, because our implementation doesn't support
DAV:contains.

Feedback appreciated.


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 Julian Reschke
> Sent: Friday, January 10, 2003 2:31 PM
> To: www-webdav-dasl@w3.org
> Subject: RE: Proposed resolution for issue "score-pseudo-property"
>
>
>
> > >>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.
>
> Proposed resolution [1]:
>
> 5.15  Limiting the result set
>
> <!ELEMENT limit (nresults) >
> <!ELEMENT nresults (#PCDATA)> ;only digits
>
> The DAV:limit XML element contains requested limits from the
> client to limit
> the size of the reply or amount of effort expended by the server. The
> DAV:nresults XML element contains a requested maximum number of
> DAV:response
> elements to be returned in the response body. The server MAY
> disregard this
> limit. The value of this element is an integer.
>
> 5.15.1  Relationship to result scoring
>
> If the result set is limited, and the response elements in the result
> document contain the DAV:score XML element (see section 5.14.1),
> the results
> that are included in the response document must be those with the highest
> search scores (the highest numerical values for DAV:score).
>
>
>
> [1]
> <http://greenbytes.de/tech/webdav/draft-reschke-webdav-search-late
st.html#rf
c.section.5.15>

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Monday, 13 January 2003 10:48:26 GMT

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