Difference between revisions of "VCard and ICal support"

(Other fields not supported)
m (ALARM: "Remind me four times")
Line 11: Line 11:
  
 
== ALARM: "Remind me four times" ==
 
== ALARM: "Remind me four times" ==
ICal allows you to set an alarm with should be repeated four times before ending. This might be interesting for an alarm clock, but for a web-based tool with will be used asynchronous in most cases, we handle this differently. Therefore, OX does not support an ALARM with a REPEAT property.
+
ICal allows you to set an alarm which should be repeated four times before ending. This might be interesting for an alarm clock, but for a web-based tool with will be used asynchronous in most cases, we handle this differently. Therefore, OX does not support an ALARM with a REPEAT property.
  
 
Behavior: This property is '''ignored'''.
 
Behavior: This property is '''ignored'''.

Revision as of 15:04, 13 August 2007

VCard and ICal are definitions of text-based PIM information in files. In OX terms, VCard defines contact data, while ICal defines both Tasks and Appointments. ICal internally identifies itself as VCalendar 2.0, which illustrates who closely related both protocols are. That is why questions on both formats are answered in one article.

This article deals with features that are in VCard and ICal but are problematic within the OX.

RRULE: "The second last sunday in a month"

ICal allows you to define an appointment with occurs "the second last sunday every month". OX simply does not. We only support counting from the beginning of a month, but not from the end. Since a month might have either four or five occurrences of a certain day, it is not possible for us to simply convert this.

Behavior: An ICal appointment containing this property is not imported.

See RFC 2445, 4.8.5.4 Recurrence Rule

ALARM: "Remind me four times"

ICal allows you to set an alarm which should be repeated four times before ending. This might be interesting for an alarm clock, but for a web-based tool with will be used asynchronous in most cases, we handle this differently. Therefore, OX does not support an ALARM with a REPEAT property.

Behavior: This property is ignored.

Reference: RFC 2445, 4.8.6.2 Repeat count

Other fields not supported

Appointments

ATTACH, COMMENT, CONTACT, CREATED, DTSTAMP, EXRULE, GEO, LAST-MODIFIED, ORGANIZER, PRIORITY, RDATE, REQUEST-STATUS, STATUS

Contacts

GEO, KEY, LABEL, LOGO, MAILER, NAME, PRODID, PROFILE, REV, SORT-STRING, SOUND, SOURCE, TZ, VERSION

Tasks

ATTACH COMMENT, CONTACT, EXDATE, EXRULE, GEO, LAST-MODIFIED, LOCATION, ORGANIZER, REQUEST-STATUS, RESOURCES, RDATE, URL