diff --git a/collection-sharing.xml b/collection-sharing.xml index deb77a3..95072e0 100644 --- a/collection-sharing.xml +++ b/collection-sharing.xml @@ -6,7 +6,7 @@ -]> +]> @@ -19,7 +19,7 @@ - Shared and Published Calendars in CalDAV + Shared and Published Calendars in CalDAV Apple Inc. @@ -29,7 +29,7 @@ 1 Infinite Loop Cupertino CA - 95014 + 95014 USA cyrus@daboo.name @@ -45,7 +45,7 @@ 1 Infinite Loop Cupertino CA - 95014 + 95014 USA @@ -118,13 +118,13 @@ --> - +
- The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in . + The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in . - When XML element types in the namespaces "DAV:" and "urn:ietf:params:xml:ns:caldav" are referenced in this document outside of the context of an XML fragment, the string "DAV:" and "CALDAV:" will be prefixed to the element type names respectively. + When XML element types in the namespaces "DAV:" and "urn:ietf:params:xml:ns:caldav" are referenced in this document outside of the context of an XML fragment, the string "DAV:" and "CALDAV:" will be prefixed to the element type names respectively. Terms Used: @@ -135,7 +135,7 @@
- +
This section provides a basic overview of this protocol by way @@ -181,13 +181,13 @@ sharee's invite status to declined.
- +
In order to facilitate the process of sharing invitations, this specification defines a new generic notification mechanism for CalDAV servers. When this feature is available, a CS:notification-URL property appears on principal resources for those principals who are able to receive notifications. That property specifies a single DAV:href element whose content refers to a WebDAV collection resource. Notification "messages" are deposited into this collection and can be retrieved by clients and acted on accordingly. - The notification collection referenced by the CS:notification-URL property MUST have a DAV:resourcetype property with DAV:collection and CS:notification child elements. + The notification collection referenced by the CS:notification-URL property MUST have a DAV:resourcetype property with DAV:collection and CS:notification child elements. Notification "messages" are XML documents stored as resources in the notification collection. Each XML document contains a CS:notification element as its root. The root element contains a CS:dtstamp element, and one additional element which represents the type of notification being conveyed in the message. That child element will typically contain additional content that describes the notification. @@ -211,7 +211,7 @@ This property SHOULD be protected. This property SHOULD NOT be returned by a PROPFIND allprop request (as defined in Section 14.2 of ). This property value SHOULD be preserved in COPY and MOVE operations. - + This property is needed for a client to determine where the notification collection of the current user is located so that processing of notification messages can occur. If not present, then the associated calendar user is not enabled for notification messages on the server.
@@ -236,7 +236,7 @@ This property MUST be protected. This property SHOULD NOT be returned by a PROPFIND allprop request (as defined in Section 14.2 of ). This property value MUST be preserved in COPY and MOVE operations. - + This property allows a client, via a PROPFIND Depth:1 request, to quickly find notification messages that the client can handle in a notification collection. The single child element is the notification resource root element's child defining the notification itself. This element MUST be empty, though any attributes on the element in the notification resource MUST be present in the property element.
@@ -280,7 +280,7 @@ This property MUST be protected. This property SHOULD NOT be returned by a PROPFIND allprop request (as defined in Section 14.2 of ). This property value MUST be preserved in COPY and MOVE operations. - + This WebDAV property is present on a calendar collection resource that has been shared by the owner, or on the calendar collection resources of the sharees of the calendar. It provides a list of users to whom the calendar has been shared, along with the "status" of the sharing invites sent to each user. In addition, servers SHOULD include a CS:organizer XML element on calendar collection resources of the sharees to provide clients with a fast way to determine who the sharer is. A server's local privacy policy may prevent sharees from knowing about other sharees on a shared calendar. If that is so server will not include CS:user XML elements for other sharees.
@@ -300,7 +300,7 @@ This property MUST be protected. This property SHOULD NOT be returned by a PROPFIND allprop request (as defined in Section 14.2 of ). This property value MUST be preserved in COPY and MOVE operations. - + This WebDAV property is present on a calendar collection resource that can been shared or published. It provides a list of options indicating what sharing modes are allowed as per .
@@ -321,7 +321,7 @@ This property MUST be protected. This property SHOULD NOT be returned by a PROPFIND allprop request (as defined in Section 14.2 of ). This property value MUST be preserved in COPY and MOVE operations. - + This WebDAV property is present on a shared calendar collection resource that appears in a sharee's calendar home collection. Its content is a single DAV:href element whose value is the URL of the sharer's calendar being shared.
@@ -359,11 +359,11 @@ When the sharee list on a shared calendar is changed, the server MUST send notifications to each sharee to update them on their current sharing status. This is accomplished by sending a CS:invite-notification notification to each sharee.
- + This example shows how to add a single sharee (with calendar user address "mailto:eric@example.com") to a shared calendar with CS:read-write access. - +
>> Request <<
- + This example shows how multiple sharee's can be manipulated in a single request. The sharee with calendar user address "mailto:eric@example.com" has their access downgraded to CS:read, whilst another sharee is removed from the access list entirely. - +
>> Request << CS:can-be-shared: when present indicates that the calendar collection can be shared. When not present, the calendar collection cannot be shared. CS:can-be-published: when present indicates that the calendar collection can be published. When not present, the calendar collection cannot be published. - + When not present on a calendar collection, sharing or publishing of that calendar is not allowed. Clients SHOULD NOT attempt to use requests to enable sharing or publishing targeted at those calendar collections. @@ -1057,7 +1057,7 @@ Date: Sat, 11 Nov 2006 09:32:12 GMT]]> &rfc3744; &rfc4791; &rfc4918; - &rfc6638; + &rfc6638;