Calendar Access Protocol (CAP)
Voir toute la rfc dans une seule page
Page : 16 / 131
Télécharger le PDF
Auteur(s) : S. Mansour
, G. Babics
, D. Royer
Classé sous : Calendar user
, Calendar user agent
, Calender store
RFC 4324 Calendar Access Protocol December 2005
EXPAND - This property tells the CS if the query reply should expand
components into multiple instances. The default is "FALSE" and is
ignored for CSs that cannot expand recurrence rules. (Section
GRANT - The UPNs listed in the "GRANT" property of a "VCAR"
component will be allowed access as described in the "VRIGHT"
component. (Section 8.17)
ITIP-VERSION - The version of [iTIP] supported. (Section 8.18)
MAXDATE - The maximum date supported by the CS. (Section 8.20)
MAX-COMP-SIZE - The largest component size allowed in the
implementation including attachments in octets. (Section 8.19)
MINDATE - The minimum date supported by the CS. (Section 8.21)
MULTIPART - Passed in the capability messages to indicate which MIME
multipart types the sender supports. (Section 8.22)
NAME - The "NAME" property is used to add locale-specific
descriptions into components. (Section 8.23)
OWNER - Each calendar has at least one "OWNER" property. (xref
target="OWNER"/>) Related to the "CAL-OWNERS()" query clause.
PERMISSION - This property specifies the permission being granted or
denied. Examples are the "SEARCH" and "MODIFY" values. (Section
QUERY - Used to hold the CAL-QUERY (Section 8.26) for the component.
QUERYID - A unique id for a stored query. (Section 8.27)
QUERY-LEVEL - The level of the query language supported. (Section
RECUR-ACCEPTED - If the implementation support recurrence rules.
RECUR-EXPAND - If the implementation support expanding recurrence
rules. (Section 8.31)
RECUR-LIMIT - Any maximum limit on the number of instances the
implementation will expand recurring objects. (Section 8.30)
Royer, et al. Experimental [Page 16]