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

[Jeffrey Harris]

Hi Brian,

> when chandler later sent an update of the event to cosmo, it would do
> a similar mapping, again sending only the subset of information that
> the eim event schema includes, and cosmo would fold those changes back
> into the original icalendar object.

That works fine as long as Chandler doesn't send out its own iCalendar
version of the event.

Can we add a way to pass back and forth this extra iCalendar data,
probably just by passing around the original VEVENT and assuming both
sides will override as appropriate?

This needn't be a short-term priority, I don't think, but post-Preview I
think we ought to be doing the right thing with iCalendar throughout the
Chandler/Cosmo ecosystem, if we're going to be trying to interoperate.

> the eim event schema doesn't support alarms at the moment. i imagine
> we'd define a separate alarm record type and relate it back to an
> event record with a foreign key column specifying the event's uuid.

OK, if such things are on your radar, great!

Sincerely,
Jeffrey