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

[Brian Moseley]

On 2/9/07, Jeffrey Harris <jeffrey at osafoundation.org> wrote:

> I think that should work fine, as long as we're all on the same page
> about what our various nulls mean.  So, to summarize, Chandler will emit
> Empty for the specific removal of a field, and None/Null for fields that
> inherit from the master (including startTime/endTime, with our common
> understanding of the meaning of inheriting these values).

this seems totally backwards.

cosmo's domain model doesn't care about inheritance. it just cares
about what properties an item has and what properties a modification
has.

eim requires a dtstart and a dtend for a master event and for an
exception event. chandler and cosmo ui should be responsible for
setting those fields in those records appropriately. chandler and
cosmo ui are the things that care about inheritance, so the burden
should be on them to do whatever needs to happen to get a dtstart and
a dtend into an exception event record.

in eim, a null field value means that value is meant to be deleted. in
eim, an empty string text value means just that - the corresponding
item or modification attribute is meant to have "" as its string
value.

let's not get eim and cosmo's storage mixed up with application features.