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

[Brian Moseley]

On 12/13/06, Jeffrey Harris <jeffrey at osafoundation.org> wrote:

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

the eim event record type defines only a limited number of columns and
does not have an extension mechanism.

cosmo would extract the icalendar properties that map to the eim event
columns and send those to chandler, ignoring any other icalendar
properties or subcomponents.

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.

> 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

same answer.

> 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.

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.