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

RE: href in where clause

From: Wallmer, Martin <Martin.Wallmer@softwareag.com>
Date: Fri, 1 Mar 2002 15:01:47 +0100
Message-ID: <DFF2AC9E3583D511A21F0008C7E6210602D8FFC6@daemsg02.software-ag.de>
To: "'Julian Reschke'" <julian.reschke@gmx.de>, dasl <www-webdav-dasl@w3.org>
Hi,

querying the display name seems not to be a good idea, as WebDAV does not
define how the display name should be derived from the href. So different
servers might produce different display names for the same href. Slide for
example encloses the display name in a CDATA section.

So something as you suggested is necessary. Whats about url encoding? It
could be something like
<D:where>
  <D:like>
    <D:href url-encoding="shift-jis"/>
    <D:literal>somethingWithSpecialCharacters</D:literal>
  </D:like>
</D:where>

url encoding should default to UFT-8

Regards,
Martin

-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@gmx.de]
Sent: Donnerstag, 28. Februar 2002 15:20
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 Friday, 1 March 2002 09:01:59 GMT

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