W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2001

RE: content type for WebDAV request/response bodies, was: [ACL] Access Control Protocol -07 submitted

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 21 Nov 2001 01:07:45 +0100
To: <mtimmerm@opentext.com>, "'WebDAV'" <w3c-dist-auth@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCEEBFDIAA.julian.reschke@gmx.de>
Matt,

> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Matt Timmermans
> Sent: Tuesday, November 20, 2001 10:49 PM
> To: 'Julian Reschke'; 'WebDAV'
> Subject: RE: content type for WebDAV request/response bodies, was: [ACL]
> Access Control Protocol -07 submitted
>
>
> Appendix 23.4 provides an unambiguous interpretation of property names as
> HREFs.  This will no longer apply when appendix 23.4 goes away.

The definition is broken. It doesn't work. See [1].

> I've seen Microsoft use a convention for coding property names as
> HREFs that
> would work well for 2518:

No, it doesn't.

> If the property's namespace ends in "/" or ":", then the property HREF is
> namespace+local_name, just like Today.
>
> Otherwise, the property HREF is namespace+"#"+local_name.

How do you encode the local name? Given an arbitrary URI, how do you select
base URI and element name? ...and so on. It doesn't work.

> WebDAV would have to codify this in the description of
> DAV:keepalive.  This
> would at least be compatible with most current environments.

I would care more if there is a single server implementation that actually
implements keepalive. Is there?

> Ideally, keepalive should be (allprop|prop), but that would break
> everybody.

Ideally, the whole behaviour of copying live/dead properties needs to be
redefined, I think.

Regards, Julian

[1] <http://mailman.webdav.org/pipermail/acl/2001-November/000929.html>
Received on Tuesday, 20 November 2001 19:08:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:59 GMT