Calendar Access Protocol (CAP)
Voir toute la rfc dans une seule page
Page : 80 / 131
Télécharger le PDF
Auteur(s) :
S. Mansour,
G. Babics,
D. Royer
Classé sous :
Calendar user,
Cu,
Calendar user agent,
Cua,
Ical,
Calender store,
Cs
RFC 4324 Calendar Access Protocol December 2005
SELECT *.* FROM VCALSTORE
9.3. VCAR Component
Component Name: VCAR
Purpose: Provide a grouping of calendar access rights.
Formal Definition: A "VCAR" component is defined by the following
notation:
carc = "BEGIN" ":" "VCAR" CRLF
carprop 1*rightc
"END" ":" "VCAR" CRLF
;
carprop = 1*(
;
; 'carid' is REQUIRED,
; but MUST NOT occur more than once
;
carid /
;
; the following are OPTIONAL,
; and MAY occur more than once
;
name / decreed / other-props
)
Description: A "VCAR" component is a grouping of properties, and
"VRIGHT" components, that represents access rights granted or
denied to UPNs.
The "CARID" property specifies the local identifier for the "VCAR"
component. The "NAME" property specifies a localizable display
name.
Example: In the following example, the UPN "foo@example.com" is given
search access to the "DTSTART" and "DTEND" VEVENT properties. No
other access is specified:
Royer, et al. Experimental [Page 80]