icalendar-implementations

(Difference between revisions)

Jump to: navigation, search
(noted some Apple iCal 2.0.5 testing results and thus implications for hCalendar processors that generate iCalendar. noted need to document more thoroughly in hcalendar-parsing page.)
(MSOutlook2k3 general comments)
Line 82: Line 82:
* UID and DTSTAMP is required for Outlook to import. [[User:GeoffWebb|GeoffWebb]] 14:03, 9 Dec 2005 (PST)
* UID and DTSTAMP is required for Outlook to import. [[User:GeoffWebb|GeoffWebb]] 14:03, 9 Dec 2005 (PST)
 +
 +
 +
======= Potential Security Related Issue ==========
 +
I've been all over the web tracing the "Lunar" error.
 +
I believe I'm come across another lunar permutation.
 +
I have an XP box running Outlook 2003 SP3 with Admin privileges, and I have an XP box running Outlook 2003 SP3 (same build number) running under a standard account.
 +
The .ics will try to import correctly under the Admin account (aka, it will prompt you for acceptance, everything working as expected).  HOWEVER, the same .ics file will throw the "lunar" exception on the ~standard~ account.
 +
 +
Here is my environment information just in case you're bumping your head on this issue.
 +
 +
To be honest, I probably will just abandon trying to use it for this project because of this issue.
 +
But I wanted to report it, so someone doesn't waste a day thinking the issue is the contents of the .ics file.
 +
 +
 +
Outlook 2003 with SP3 Build Number : 11.8325.8329
 +
 +
.ics file contents
 +
 +
BEGIN:VCALENDAR
 +
VERSION:2.0
 +
PRODID:www.testMeiCalendar.net
 +
METHOD:REQUEST
 +
BEGIN:VEVENT
 +
DTSTART:20101231T230000
 +
DTEND:20110101T010000
 +
SUMMARY:New Years Eve Reminder
 +
LOCATION:Downtown
 +
DESCRIPTION:Let's get together for New Years Eve
 +
UID:ABCD1234-188C-4960-BBB7-FC9917453394
 +
SEQUENCE:0
 +
DTSTAMP:20101125T112600
 +
END:VEVENT
 +
END:VCALENDAR
===== MSOutlook2k3 sample importable iCalendar =====
===== MSOutlook2k3 sample importable iCalendar =====

Revision as of 19:05, 22 November 2010

iCalendar implementations

Contents

This is a list of calendar programs, applications and services that support the iCalendar RFC2445 standard.

In addition, please note any quirks or bugs with implementations' handling of iCalendar - we've already discovered some in the development of hCalendar and proxies like X2V.

services

Google Calendar

http://calendar.google.com/

products

Apple iCal

Apple iCal application aka iCal.app.

Apple iCal 2.0.5

Apple iCal.app 2.0.5 build 1069 (AppleiCal205)

AppleiCal205 notes

As a result Apple iCal 2.0.5 ignores date and date-time properties (e.g. DTSTART, DTEND, etc.) when date components (year, month, day) are separated by "-" or when time components (hours, minutes, seconds) are separated by ":" (both as allowed by ISO8601 and required by RFC3339).

However per accessibility research, dates and times with separators are more readable and accessible, and consequently explicitly allowed by hCalendar.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date and date-time properties (e.g. DTSTART, DTEND, etc.) with separators, and remove separators when converting to iCalendar.

However in practice (see hcalendar-examples-in-wild) hCalendar date-time properties often omit the seconds because when they are "00" for simplicity and easier/quicker readability.

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) without the seconds explicitly specified, and imply "00" seconds when converting to iCalendar.

However, in practice (see hcalendar-examples-in-wild) hCalendar date-time properties often state the timezone offset in order to make the human visible time consistent with the machine readable time for easier verification (minimize DRY divergence probability).

Thus hCalendar processors which generate iCalendar files MUST handle parsing hCalendar date-time properties (e.g. DTSTART, DTEND, etc.) with an explicit timezone offset, and convert the specified date-time value to a UTC value when converting to iCalendar.

All hCalendar processor requirements above should be documented thoroughly in hcalendar-parsing.

KOrganizer

Evolution

Sunbird

Mozilla Sunbird

Microsoft Outlook

Microsoft Outlook 2007

Microsoft Outlook 2007 (MSOutlook2k7)

Microsoft Outlook 2003

Microsoft Outlook 2003 (MSOutlook2k3)

MSOutlook2k3 general comments

For importing, MSOutlook2k3 apparently requires VEVENTS to have UID, DTSTAMP, and METHOD properties. (citation/platform/date tested info needed). If any of the three is not present, returns this message:

This error can appear if you have attempted to save a recurring Lunar appointment in iCalendar format.
To avoid this error, set the appointment option to Gregorian instead of Lunar.

After some testing, this seems to be the generic message to indicate a problem with event import.

No such restriction is placed on vCalendar 1.0 events. So, if VERSION:1.0 is output instead of VERSION:2.0, the only required field is DTSTART. Note that VERSION property may be omitted. In this case, value inferred as 1.0.


= Potential Security Related Issue ====

I've been all over the web tracing the "Lunar" error. I believe I'm come across another lunar permutation. I have an XP box running Outlook 2003 SP3 with Admin privileges, and I have an XP box running Outlook 2003 SP3 (same build number) running under a standard account. The .ics will try to import correctly under the Admin account (aka, it will prompt you for acceptance, everything working as expected). HOWEVER, the same .ics file will throw the "lunar" exception on the ~standard~ account.

Here is my environment information just in case you're bumping your head on this issue.

To be honest, I probably will just abandon trying to use it for this project because of this issue. But I wanted to report it, so someone doesn't waste a day thinking the issue is the contents of the .ics file.


Outlook 2003 with SP3 Build Number : 11.8325.8329

.ics file contents

BEGIN:VCALENDAR VERSION:2.0 PRODID:www.testMeiCalendar.net METHOD:REQUEST BEGIN:VEVENT DTSTART:20101231T230000 DTEND:20110101T010000 SUMMARY:New Years Eve Reminder LOCATION:Downtown DESCRIPTION:Let's get together for New Years Eve UID:ABCD1234-188C-4960-BBB7-FC9917453394 SEQUENCE:0 DTSTAMP:20101125T112600 END:VEVENT END:VCALENDAR

MSOutlook2k3 sample importable iCalendar
BEGIN:VCALENDAR
VERSION:2.0
METHOD:PUBLISH
BEGIN:VEVENT
UID:0
DTSTAMP:20060601T080000
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR
MSOutlook2k3 sample importable vCalendar
BEGIN:VCALENDAR
BEGIN:VEVENT
DTSTART:20060601T080000
END:VEVENT
END:VCALENDAR

notes

contributors

related pages

This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.

icalendar-implementations was last modified: Wednesday, December 31st, 1969

Views