[Cosmo-dev] Re: changing the format of modification recurrence-ids in eim

[Jeffrey Harris]

>> "f2953300-6fcb-4547-ad7b-22e193b6903f::;VALUE=DATE-TIME:20070511T090000",
>> would turn into something like
>> "f2953300-6fcb-4547-ad7b-22e193b6903f:1178666002".
>> ...
>> morgen, grant, randy - thoughts?
> 
> Sounds fine to me, though I'd be a little more in favour of something like:
> 
> f2953300-6fcb-4547-ad7b-22e193b6903f:20070511T090000Z
> 
> (i.e. an ISO UTC date-time rather than a timestamp). But, either way.

Yeah, I think we still need the range of timezoned (expressed in UTC),
floating, and all-day, so

20070511T090000Z
or
20070511T090000
or
20070511

With that said, I'm in favor of this, it's much more attractive and I
think it'll solve a few lingering timezone issues.  It'll mean I have to
rewrite some of the icalendar<->EIM code and tweak a bunch of tests, but
it's not a ton of work.

I'm a little confused how this could require no change to Cosmo, seems
like if someone PUTs an iCalendar file with a recurring event and a
modification in a Cosmo collection, Cosmo has to decide which
pseudo-uuid to use for the modification if a Chandler client comes along
and queries that collection using Morse Code.

Is there a mechanism for a Chandler client to declare what Morse Code
version it's using, so Cosmo can vary its output based on the client?

Sincerely,
Jeffrey