In section 3 Privileges of RFC3744 <http://tools.ietf.org/html/rfc3744#section-3> it says: Aggregate and non-aggregate privileges are both capable of being abstract. but in section 5.4 DAV:current-user-privilege-set of RFC3744 <http://tools.ietf.org/html/rfc3744#section-5.4> it says: Therefore, each element in the DAV:current-user-privilege-set property MUST identify a non-abstract privilege from the DAV:supported-privilege-set property. In a discussion amongst CalDAV implementors, it was brought up that the above requirement would be problematic for implementations that supports non-aggregate "abstract" privileges. That is, an implementation that allows such a privilege to be set individually on a resource (either by default or through a proprietary mechanism) would not be allowed to report this privilege in the DAV:current-user-privilege-set property. Cheers, BernardReceived on Friday, 15 May 2009 13:42:52 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:17 GMT