[Cosmo-dev] custom iCalendar data in an EIM world

[Jeffrey Harris]

Hi Folks,

I'm working on bug 6702, get Chandler to stop throwing away iCalendar
data it doesn't understand.

On the surface, this is fairly easy, we can just keep the original
iCalendar stream, when we serialize re-use anything we didn't change.

I'm wondering how this will work in the EIM universe, though.  Seems
like there are two parallel use cases we should look at together:

Tom PUTs a VEVENT to Cosmo using iCal/CalDAV, with a bunch of X-APPLE
properties, then Chandler downloads that event using EIM

vs.

Tom emails me a VEVENT using iCal, I put it up on Cosmo using EIM, then
Tom grabs the event back using using CalDAV, hoping not to have lost all
his spiffy custom X-APPLE properties

Do we have a plan for harmonizing this stuff?

On a related note, iCalendar models alarms as sub-objects of events,
whereas Chandler models them as separate, linked items.  I'm not sure
how that'll work for Cosmo's CalDAV implementation when we're publishing
items using EIM.

Sincerely,
Jeffrey