[Cosmo-dev] Recurrence modifications, filters, and diffs

Randy Letness randy at osafoundation.org
Fri Feb 9 08:24:50 PST 2007


Jeffrey Harris wrote:
> I'd like the conversion to/from icalendar from/to EventModification
> records to handle no value in modifications smoothly.  I think this means:
>
> - Putting a DTSTART and a DTEND into icalendar even if they weren't changed
> - NOT putting DTSTART and DTEND into EIM unless start time or duration
> was changed by the modification
>   
We could do this.  Cosmo would just have to do some extra calculations 
using the recurrence id and master event's start/end time (duration).  
So if an event is created via CalDAV that includes start/end times for 
all modifications does this mean you want Cosmo to strip the unnecessary 
start/end times when Chandler syncs (only send start/end if they weren't 
changed)?

> Finally, I think we need a third (or a forth?) kind of null value for
> EIM, there's already empty string vs. empty record vs. No Change, this
> is "no attribute modification", or inherit from the master.
>
>   

Is this something Chandler needs?  Cosmo could just treat regular null 
or "no change" as inherit from the master.

-Randy


More information about the cosmo-dev mailing list