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

RE: href in where clause

From: Lisa Dusseault <lisa@xythos.com>
Date: Thu, 28 Feb 2002 09:36:01 -0800
To: "'Julian Reschke'" <julian.reschke@gmx.de>, "'dasl'" <www-webdav-dasl@w3.org>
Message-ID: <01b101c1c07e$6d008f10$f8cb90c6@moose>
A related problem, perhaps for RFC2518, is how displayname should be used.
If displayname is only the final path segment or filename of a href (as most
products seem to be implemented), then displayname might be sufficient for
most of the kinds of searches you could do with href.

Lisa

> -----Original Message-----
> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Julian Reschke
> Sent: Thursday, February 28, 2002 6:20 AM
> To: dasl
> Subject: DAV:href in where clause
>
>
> DAV:href isn't a property, so it can't be used in queries.
>
> Is this a problem? Examples where DAV:displayname is queried
> instead seem to
> indicate that. A possible solution would be to allow DAV:href
> whereever
> DAV:prop is allowed in the where clause.
>
> For instance:
>
> <D:where>
>   <D:like>
>     <D:href/>
>     <D:literal>%.doc</D:literal>
>   </D:like>
> </D:where>
>
> Of course it would be a problem that WebDAV is silent about
> the allowed
> formats that can appear in the href element (authority
> mandatory? which
> forms of relative URI references are allowed and interoperable?).
>
Received on Thursday, 28 February 2002 12:35:32 GMT

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