[Ietf-caldav] Scheduling section 3.1.1 (again)

Mike Douglass douglm at rpi.edu
Mon Sep 29 10:40:21 PDT 2008


You have the text:

   The DAV:resourcetype property on a calendar collection MUST be
   immutable.  Once a calendar collection has been created, servers MUST
   NOT change it from a scheduling calendar collection to a basic
   calendar collection, or vice versa.


Why and from a client perspective how is this enforced?

User has non-scheduling calendar X
Moves the contents to Y
Deletes X
Recreates X as scheduling calendar
Moves Y/* back into X

or alternatively just does a PROPPATCH



-- 

Mike Douglass                           douglm at rpi.edu
Senior Systems Programmer
Communication & Collaboration Technologies      518 276 6780(voice) 2809
(fax)
Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180



More information about the Ietf-caldav mailing list