W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2003

RE: bind draft issues

From: Clemm, Geoff <gclemm@rational.com>
Date: Mon, 10 Mar 2003 09:08:59 -0500
Message-ID: <E4F2D33B98DF7E4880884B9F0E6FDEE2021C5F85@SUS-MA1IT01>
To: WebDAV <w3c-dist-auth@w3.org>, "Roy T. Fielding" <fielding@apache.org>

   From: Julian Reschke [mailto:julian.reschke@gmx.de]

   Geoff, as RFC3253 relies on the concept of bindings, could you
   please attempt to fill in what *you* think an identical
   DAV:resource-id needs to indicate?

For RFC3253, two version-controlled resources are the "same" when
they have the same version history.  So the obvious implementation
of the DAV:resource-id property for a version-controlled resources
is the DAV:version-history property.

Version and Version-History resources cannot be moved, so the
URL at which the were created can act as their DAV:resource-id.

So this allows RFC3253 to remain neutral on the question of 
what does "resource identity" mean about the results of various
other HTTP and WebDAV methods.

Note: the question of resource identity for an activity resource
is not addressed by RFC3253, so that remains an open question.
Since most versioning repositories store activity resources in some
kind of database, resource identity for activities ends up not
being much of a problem in practice though, since there usually will
be some obvious implementation property that could be used as
the DAV:resource-id property.

Received on Monday, 10 March 2003 09:09:15 UTC

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