[Ietf-calsify] Re: Google Speculation, but interesting

[Cameron Stillion]

While I appreciate the semantic difference between these two application
verbs - most users are not quite that savvy. The result? Most of the ics
files published to apple.com (and icalshare.com) are NOT of the
Export... flavor - and that means most people are not including what is
needed for interop.  You must admit it is at least user unintuitive, and
at worst a little sloppy.

cameron

-----Original Message-----
From: ietf-calsify-bounces at osafoundation.org
[mailto:ietf-calsify-bounces at osafoundation.org] On Behalf Of Cyrus Daboo
Sent: Sunday.27.February.2005 06.37
To: Cameron Stillion; pregen at egenconsulting.com;
Robert_Ransdell at notesdev.ibm.com
Cc: Calsify; www-rdf-calendar at w3.org
Subject: RE: [Ietf-calsify] Re: Google Speculation, but interesting

Hi Cameron,

--On February 26, 2005 11:18:05 PM -0800 Cameron Stillion
<camerost at exchange.microsoft.com> wrote:

> The behavior I have seen in the latest Apple iCal (the product) with 
> regard to timezones is that they are NOT defined in VTIMEZONE blocks, 
> but are named in VEVENTS.  The names seem to match the OSX naming 
> comventions for Time Zones, and notably do not match the Windows
names.
> Since they aren't formally defined, it's difficult to map them.  We 
> are forced to have an internal list of Apple names for the sole 
> purpose of interoping.  (grumble grumble)
>

Right - I just did a test and indeed if you create a new calendar and
add a single event with a timezone, it does not include the VTIMEZONE in
the ics file it creates in its own calendar store. However, if you
'Export' the calendar from the iCal.app, then it does include a
VTIMEZONE. The VTIMEZONE appears to be correct, but contains only the
minimum amount of information to cover the time for the event. Arguably
this is not a bug as it is free to do whatever it wants in its own
calendar store.

WRT naming of timezones on different OS's - hopefully with a
standardised timezone registry we can solve that issue and also remove
the need to always send the VTIMEZONE data by value (as opposed to by
reference to the registry entry).

--
Cyrus Daboo
_______________________________________________
Ietf-calsify mailing list
Ietf-calsify at osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/ietf-calsify