W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > October to December 2002

RE: workspace property

From: Clemm, Geoff <gclemm@rational.com>
Date: Tue, 1 Oct 2002 14:30:27 -0400
Message-ID: <E4F2D33B98DF7E4880884B9F0E6FDEE25ED430@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
No, the DAV:workspace is not affected by the request-URL that you
use to identify the URL (that would be bad for a variety of reasons).
The only way you can have two different URLs for the same resource is
if you have two bindings to either the resource or to a parent of the
resource.  In this case, some resource has multiple parents, and which
parent is picked for inheritance of the DAV:workspace property is up to
the server (but it has to pick one, and return it consistently).

So the answer was: (d) None of the above (:-).

Cheers,
Geoff

-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@greenbytes.de]
Sent: Tuesday, October 01, 2002 1:49 PM
To: ietf-dav-versioning@w3.org
Subject: DAV:workspace property



Hi,

a very basic question...

The workspace feature introduces a live (protected) resource property which
seems to depend on the URI of the resource, not the resource itself:

" If the request-URL did not identify a workspace, the DAV:workspace of the
destination MUST have been updated to have the same value as the
DAV:workspace of the parent collection of the destination."

To me this seems to indicate that it's not really a property of the resource
itself, but that it only depends on how you access the resurce.

How does this property affect bindings to a resource in a workspace?

a) there may be no additional bindings

b) there may be additional bindings, but they must all reside in the same
workspace's namespace

c) there may be additional bindings, and the reported DAV:workspace property
just depends on the URI used in the request

(I currently lean towards c)


Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Tuesday, 1 October 2002 14:31:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:43 GMT