[Cosmo-dev] cosmo 0.6.1 EIMML changes

[Jeffrey Harris]

Hi Randy,

> This means the note record now has a parentUuid field, which is the
> uuid of the master note.  So instead of including all the
> note/contentitem info(body, triageStatus, reminderTime, etc) in the
> eventModification record, separate contentitem/note records should be
> used (with the note record containing the parent uuid of the master
> note item).

Gosh, I wish we'd had more in depth notes from our meeting, there was a
lot that was flying by.

We definitely discussed doing this, but my memory is that we ultimately
decided against it and specifically planned on including note fields in
EventModification records.  I think the reason was that we don't want to
send around UUIDs for modifications, because modifications are uniquely
determined by master uuid and recurrence-id, passing around different
Chandler's varying concepts of the modification's UUID is a recipe for
disaster.  So I think the keys for modifications need to be the master's
UUID and the modification's recurrence-id, not the modification's UUID.

It seems OK to me to have a NoteModification record separate from
EventModification, but I'm attached to not passing around UUIDs for
modifications, so in your EventModification example, I think instead of
eventModification:uuid we need eventModification:parentUuid, and in
NoteModification we need to remove the uuid field and add a
recurrence-id field.

Sincerely,
Jeffrey