RFC 4791:Calendaring Extensions to WebDAV (CalDAV)
RFC-Ref

WebDAV


Click on the red underlined text to get to the source

... The concept of using HTTP [RFC2616] and WebDAV [RFC2518] as a basis for a calendar access protocol ...
... iCalendar [RFC2445] objects, and using WebDAV to get listings of resources. However, those implementations do not interoperate because there are many small and big decisions to be made in how to model calendaring data as WebDAV ...
... WebDAV to get listings of resources. However, those implementations do not interoperate because there are many small and big decisions to be made in how to model calendaring data as WebDAV resources, as well as how to implement required features that aren't already part of WebDAV ...
... WebDAV resources, as well as how to implement required features that aren't already part of WebDAV. This document proposes a way to model calendar data in WebDAV ...
... WebDAV. This document proposes a way to model calendar data in WebDAV, with additional features to make an interoperable calendar access protocol. ...
... XML element types. Some of the declarations refer to XML elements defined by WebDAV [RFC2518], which use the "DAV:" namespace ...
... Also note that some CalDAV XML element names are identical to WebDAV XML element names, though their namespace ...


... object resource format; o MUST support WebDAV Class 1 [RFC2518] (note that [rfc2518bis ...
... interoperability); o MUST support WebDAV ACL [RFC3744] with the additional privilege ...
... object resources for the calendaring reports in the DAV:supported- report-set property, as defined in Versioning Extensions to WebDAV [RFC3253]. ...


... One of the features that has made WebDAV a successful protocol is its firm data model. This makes it a useful framework ...
... As a brief overview, a CalDAV calendar is modeled as a WebDAV collection with a defined structure; each calendar collection ...
... calendar collection can be individually locked and have individual WebDAV properties. Requirements derived from this model are provided in Section 4.1 and Section 4.2. ...
... A CalDAV server is a calendaring-aware engine combined with a WebDAV repository. A WebDAV repository is a set of WebDAV collections, ...
... A CalDAV server is a calendaring-aware engine combined with a WebDAV repository. A WebDAV repository is a set of WebDAV collections, containing other WebDAV ...
... CalDAV server is a calendaring-aware engine combined with a WebDAV repository. A WebDAV repository is a set of WebDAV collections, containing other WebDAV resources, within a unified URL ...
... WebDAV repository is a set of WebDAV collections, containing other WebDAV resources, within a unified URL namespace. ...
... URL namespace. For example, the repository "http://www.example.com/webdav/" may contain WebDAV collections and resources, all of which have URLs ...
... For example, the repository "http://www.example.com/webdav/" may contain WebDAV collections and resources, all of which have URLs beginning with "http://www.example.com/webdav ...
... WebDAV collections and resources, all of which have URLs beginning with "http://www.example.com/webdav/". Note that the root URL ...
... root URL, "http://www.example.com/", may not itself be a WebDAV repository (for example, if the WebDAV support is implemented through a servlet ...
... URL, "http://www.example.com/", may not itself be a WebDAV repository (for example, if the WebDAV support is implemented through a servlet or other Web server extension). ...
... Web server extension). A WebDAV repository MAY include calendar data in some parts of its URL ...
... namespace, and non-calendaring data in other parts. A WebDAV repository can advertise itself as a CalDAV server if it supports the functionality defined in this specification at any point ...


... calendar collection is manifested to clients as a WebDAV resource collection identified by a URL. A calendar ...
... calendar object resources and collections when using standard WebDAV techniques to examine the contents of a collection. b. Collections contained in calendar ...


... CalDAV servers MUST support and adhere to the requirements of WebDAV ACL [RFC3744 ...
... ACL [RFC3744]. WebDAV ACL provides a framework for an extensible set ...
... framework for an extensible set of privileges that can be applied to WebDAV collections and ordinary resources. CalDAV servers MUST also support the calendaring ...
... This section defines an additional property for WebDAV principal resources, as defined in [RFC3744 ...
... Purpose: Identifies the URL of any WebDAV collections that contain calendar collections owned by the associated principal ...


... A CalDAV client can request particular WebDAV property values, all WebDAV property values, or a list of the names of the resource's ...
... client can request particular WebDAV property values, all WebDAV property values, or a list of the names of the resource's WebDAV properties. A CalDAV ...
... WebDAV property values, or a list of the names of the resource's WebDAV properties. A CalDAV client can also request calendar data ...
... object resources that match a specified filter. The response of this report will contain all the WebDAV properties and calendar object resource data specified in the request. In the case of the CALDAV ...
... PROPFIND. In particular, the request can include XML elements to request WebDAV properties to be returned. When that occurs, the response should follow the same behavior as PROPFIND ...


... WebDAV already provides functionality required to synchronize a collection or set of collections, to make changes offline, and provides a simple way to resolve conflicts when reconnected. ETags ...
... provides a simple way to resolve conflicts when reconnected. ETags are the key to making this work, but these are not required of all WebDAV servers. Since offline functionality is more important to calendar applications than to some other WebDAV ...
... WebDAV servers. Since offline functionality is more important to calendar applications than to some other WebDAV applications, CalDAV servers MUST support ETags, as specified in Section 5.3.4. ...
... WebDAV locks can be used to prevent two clients that are modifying the same resource from either overwriting each others' changes ...
... calendar collection. The client may also be able to browse WebDAV collections to find calendar collections. ...
... the OPTIONS response to that URL to determine what can be done with it. This is somewhat of a barrier for WebDAV usage as well as with CalDAV usage. This specification does not offer a way through this ...
... the principal namespace required by WebDAV ACL support. For other cases, the authors have no universal solution, but implementers ...
... Because CalDAV requires servers to support WebDAV ACL [RFC3744], ...
... Principal-URL of the current user. Using this, a WebDAV client can learn "who am I" and ...


... caldav Purpose: Specifies a request that includes the WebDAV property values to be set for a calendar collection resource when it is ...
... DAV:prop XML element as if it were a WebDAV property. However, the CALDAV:calendar-data XML element ...
... calendar-data XML element is not a WebDAV property and, as such, is not returned in PROPFIND responses, nor used in PROPPATCH ...


... are not present in HTTP [RFC2616] and WebDAV [RFC2518], [RFC3253], ...


... Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D. Jensen, "HTTP Extensions for Distributed Authoring -- WEBDAV", RFC 2518prop, February 1999. ...
... Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J. Whitehead, "Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)", RFC 3253prop, March 2002. ...
... Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol", RFC 3744prop, May 2004. ...
... Dusseault, L., "HTTP Extensions for Distributed Authoring - WebDAV", Work in Progress, December 2006. ...


... The following table extends the WebDAV Method Privilege Table ...



Google
Web
RFC-Ref