Web DAV

目录
一、 理论
1. 对象
A. Calendar
B. Calendar Collection
2. 方法
A. OPTIONS 问询（支持与允许项目）
B. PROPFIND 查询
C. REPORT 报告
D. MKCOL 创建集合
E. 创建日历
F. PUT
G. PROPPATCH
H. DELETE
3. 响应内容与代码
二、 实务
1. iCloud
2. 189.cn
3. 139.com

一、 理论
1. 对象
A. Calendar
   Calendar object resources contained in calendar collections MUST NOT   contain more than one type of calendar component (e.g., VEVENT,   VTODO, VJOURNAL, VFREEBUSY, etc.) with the exception of VTIMEZONE   components, which MUST be specified for each unique TZID parameter   value specified in the iCalendar object.  For instance, a calendar   object resource can contain one VEVENT component and one VTIMEZONE   component, but it cannot contain one VEVENT component and one VTODO   component.  Instead, the VEVENT and VTODO components would have to be   stored in separate calendar object resources in the same collection.    Calendar object resources contained in calendar collections MUST NOT   specify the iCalendar METHOD property.    The UID property value of the calendar components contained in a   calendar object resource MUST be unique in the scope of the calendar   collection in which they are stored.    Calendar components in a calendar collection that have different UID   property values MUST be stored in separate calendar object resources.    Calendar components with the same UID property value, in a given   calendar collection, MUST be contained in the same calendar object   resource.  This ensures that all components in a recurrence “set” are   contained in the same calendar object resource.  It is possible for a   calendar object resource to just contain components that represent   “overridden” instances (ones that modify the behavior of a regular   instance, and thus include a RECURRENCE-ID property) without also   including the “master” recurring component (the one that defines the   recurrence “set” and does not contain any RECURRENCE-ID property).    For example, given the following iCalendar object:    BEGIN:VCALENDAR   PRODID:-//Example Corp.//CalDAV Client//EN   VERSION:2.0   BEGIN:VEVENT   UID:1@example.com   SUMMARY:One-off Meeting   DTSTAMP:20041210T183904Z   DTSTART:20041207T120000Z   DTEND:20041207T130000Z   END:VEVENT   BEGIN:VEVENT   UID:2@example.com   SUMMARY:Weekly Meeting   DTSTAMP:20041210T183838Z   DTSTART:20041206T120000Z   DTEND:20041206T130000Z   RRULE:FREQ=WEEKLY   END:VEVENT   BEGIN:VEVENT   UID:2@example.com   SUMMARY:Weekly Meeting   RECURRENCE-ID:20041213T120000Z   DTSTAMP:20041210T183838Z   DTSTART:20041213T130000Z   DTEND:20041213T140000Z   END:VEVENT   END:VCALENDAR    The VEVENT component with the UID value “1@example.com” would be   stored in its own calendar object resource.  The two VEVENT   components with the UID value “2@example.com”, which represent a   recurring event where one recurrence instance has been overridden,   would be stored in the same calendar object resource. 

B. Calendar Collection
   A calendar collection contains calendar object resources that   represent calendar components within a calendar.  A calendar   collection is manifested to clients as a WebDAV resource collection   identified by a URL.  A calendar collection MUST report the DAV:   collection and CALDAV:calendar XML elements in the value of the DAV:   resourcetype property.  The element type declaration for CALDAV:   calendar is: