[Cosmo-dev] Re: changing the format of modification recurrence-ids
in eim
Randy Letness
randy at osafoundation.org
Tue May 8 18:52:53 PDT 2007
Brian Moseley wrote:
>
> jeffrey and i came up with the idea of representing the recurrence-id
> part of the modification uuid as a utc timestamp rather than as
> icalendar-like value with embedded properties and internal delimiters
> and so on. so the example from bug 9054,
> "f2953300-6fcb-4547-ad7b-22e193b6903f::;VALUE=DATE-TIME:20070511T090000",
> would turn into something like
> "f2953300-6fcb-4547-ad7b-22e193b6903f:1178666002".
>
Why didn't we think of that before, duh. It will require changes in
cosmo but they should be minimal. So does this mean a RECURRENCE-IDs
should be serialized in icalendar as a UTC date/time or should the
timezone still be included if the master's start date has a timezone?
So for example:
master event:
uid = abc
startDate = ;VALUE=DATE-TIME;TZID=America/Los_Angeles:20070511T090000
modification
uid = abc:1178666002
When the modification is serialized as icalendar should RECURENCE_ID be:
;VALUE=DATE-TIME;TZID=America/Los_Angeles:20070511T090000
or
;VALUE=DATE-TIME;20070511T160000Z
-Randy
More information about the cosmo-dev
mailing list