Calendar Access Protocol (CAP)
Voir toute la rfc dans une seule page
Page : 34 / 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
; "FROM" clause.
;
; SELECT ORGANIZER FROM VEVENT ...
;
; OR
;
; A component name ('comp-name') of an existing
; component contained inside of the 'comp-name'
; used in the "FROM" clause.
;
; SELECT VALARM FROM VEVENT ...
;
; OR
;
; A component name ('comp-name') of an existing
; component contained inside of the 'comp-name' used
; in the "FROM" clause followed by a property
; name ('cap-prop') to be selected from that
; component.
; (comp-name "." cap-prop)
; SELECT VALARM.TRIGGER FROM VEVENT ...
cap-col = comp-name
/ comp-name "." cap-prop
/ cap-prop
comp-name = "VEVENT" / "VTODO" / "VJOURNAL" / "VFREEBUSY"
/ "VALARM" / "DAYLIGHT" / "STANDARD" / "VAGENDA"
/ "VCAR" / "VCALSTORE" / "VQUERY" / "VTIMEZONE"
/ "VRIGHT" / x-comp / iana-comp
cap-prop = ; A property that may be in the 'cap-comp' named
; in the "SELECT" clause.
cap-expr = "(" cap-expr ")"
/ cap-term
cap-term = cap-expr SP cap-logical SP cap-expr
/ cap-factor
cap-logical= "AND" / "OR"
cap-factor = cap-colval SP cap-oper SP col-value
/ cap-colval SP "LIKE" SP col-value
/ cap-colval SP "NOT LIKE" SP col-value
/ cap-colval SP "IS NULL"
/ cap-colval SP "IS NOT NULL"
Royer, et al. Experimental [Page 34]