W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 2002


From: Roy T. Fielding <fielding@apache.org>
Date: Fri, 10 May 2002 19:17:22 -0700
Cc: "Lisa Dusseault" <ldusseault@xythos.com>, "Webdav WG (E-mail)" <w3c-dist-auth@w3c.org>
To: "Jason Crawford" <ccjason@us.ibm.com>
Message-Id: <3A416F44-6485-11D6-8D16-000393753936@apache.org>
> I'd like to mark it resolved that we will remove the source property.  I
> would leave it up to our memories to bring the topic up again in the next
> version of WebDAV if we value it.
> The thinking is...
> The source property is good.
> But it's under specified and needs work, no interoperability has been
> determined, and no one has been yelling for it.  If we remove it from the
> spec now, the few implementations that support it can remove that support
> and thus provide us a clean slate to work from when we take another stab 
> at
> the source property.

If the source property is removed, then how will the server respond to a
client that attempts to use DAV on a resource that is not DAV authorable
but is derived from other sources?  What is the interoperability mechanism?
I would prefer a source Link solution, myself, since that can be supplied
in a normal HTTP error response.

In my opinion, WebDAV needs to solve this issue before progressing on
the standards track.  It cannot simply remove it without abandoning the
pretense that it handles Web authoring.


Roy T. Fielding, Chairman, The Apache Software Foundation
                  (fielding@apache.org)  <http://www.apache.org/>

                  Chief Scientist, Day Software
                  2 Corporate Plaza, Suite 150
                  Newport Beach, CA 92660-7929   fax:+1.949.644.5064
                  (roy.fielding@day.com) <http://www.day.com/>
Received on Friday, 10 May 2002 22:22:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:25 UTC