W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > April to June 2003

DeltaV and ACL

From: Nevermann, Dr., Peter <Peter.Nevermann@softwareag.com>
Date: Mon, 2 Jun 2003 13:48:30 +0200
Message-ID: <DFF2AC9E3583D511A21F0008C7E6210605C47F00@daemsg02.software-ag.de>
To: "'ietf-dav-versioning@w3.org'" <ietf-dav-versioning@w3.org>
Cc: "Hermann, Eckehard" <Eckehard.Hermann@softwareag.com>

On behalf of Eckehard Hermann:

Hi all,

we implemented the DeltaV and ACL extensions in our WebDAV server and now
clients are having problems in defining access rights on versioning
resources, i.e. VHR and VR resources (im particular, in view of
auto-versioning).
For example:
- how to protect /history/* without hindering auto-versioning?
- shouldn't access rights on a VCR imply access right on the associated
VR/VHR?

The DeltaV spec just touches the theme in section 16 and the ACL spec does
not mention versioning resources at all.

As VHRs and VRs are usually implicitly created while operating on VCRs
(VERSION-CONTROL, CHECKOUT, CHECKIN, auto-versioning) it should be specified
how access rights are initialized on these resources (e.g. is the DAV:acl
property to be copied to the newly created VR on CHECKIN?). 

In view of ACL inheritance over the namespace hierarchy, we believe that
integrating DeltaV and ACL is not a trivial theme and should be addressed in
either the ACL or the DeltaV spec.

Regards
Eckehard Hermann
Received on Monday, 2 June 2003 07:48:37 GMT

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