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

RE: [ACL] Standard privileges for DeltaV operations?

From: Clemm, Geoff <gclemm@rational.com>
Date: Tue, 2 Oct 2001 16:48:37 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B103F8AC28@SUS-MA1IT01>
To: acl@webdav.org, ietf-dav-versioning@w3.org
Note though that DAV:write access to the workspace and activity
collections is likely to be sufficient for controlling who can
create workspaces or activities.

Cheers,
Geoff

-----Original Message-----
From: Eric Sedlar [mailto:eric.sedlar@oracle.com]
Sent: Tuesday, October 02, 2001 2:42 PM
To: Clemm, Geoff; acl@webdav.org; ietf-dav-versioning@w3.org
Subject: RE: [ACL] Standard privileges for DeltaV operations?


Actually, I think that the privileges that are needed for versioning will
control things like who can create workspaces, activities, etc., as write
should cover checkin/checkout.

-----Original Message-----
From: acl-admin@webdav.org [mailto:acl-admin@webdav.org]On Behalf Of Clemm,
Geoff
Sent: Tuesday, October 02, 2001 10:19 AM
To: acl@webdav.org; ietf-dav-versioning@w3.org
Subject: RE: [ACL] Standard privileges for DeltaV operations?

I think it is too early to guess what an interoperable set of versioning
privileges would be.  In particular, it is unlikely that the underlying
repository privileges will be in terms of the particular methods that we
introduced in DeltaV.  There is likely to be a "read" and
"write" privilege, but not nearly as likely to be a separate "checkin" vs.
"uncheckout" privilege (i.e. you can checkin, but you can't uncheckout,
or vica versa).

So I'd suggest sticking with the generic privileges that we currently have
(i.e. DAV:read, DAV:write, etc).

Cheers,
Geoff

-----Original Message-----
From: Jim Whitehead [mailto:ejw@cse.ucsc.edu]
Sent: Tuesday, October 02, 2001 1:07 PM
To: acl@webdav.org; ietf-dav-versioning@w3.org
Subject: [ACL] Standard privileges for DeltaV operations?


So, now that the DeltaV specification has been approved, it begs the
question of whether the Access Control Protocol should define some access
privileges for versioning operations.

The following privileges make sense to me:

DAV:checkout - controls CHECKOUT
DAV:checkin - controls CHECKIN
DAV:uncheckout - controls UNCHECKOUT
DAV:report - controls REPORT
DAV:version-control - controls VERSION-CONTROL

So, minimally we would cover versioning capability, where I'm hoping there
is a lot of commonality among the access control mechanisms of existing
repositories.

Thoughts?

- Jim


_______________________________________________
acl mailing list
acl@webdav.org
http://mailman.webdav.org/mailman/listinfo/acl

_______________________________________________
acl mailing list
acl@webdav.org
http://mailman.webdav.org/mailman/listinfo/acl
Received on Tuesday, 2 October 2001 16:49:42 GMT

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