[Cosmo-dev] cosmo 0.6.1 EIMML changes

[Jeffrey Harris]

Hi Brian,

> heh, i don't remember that at all. i certainly would have argued against
> it.

I think that marathon meeting passed the "productive, everyone's
engaging" stage and entered the "whatever, please lets just be done"
stage, which is obviously not a good way to make decisions.

> wait a minute. a modification is an item in chandler, right? so why
> would different chandlers have different notions of a modification's
> uuid?

This is a key point.  From the recurrence layer's perspective, a
modification isn't really just an item.  It's the manifestation of a
particular occurrence, which is defined by the master and the recurrence
rule.  So of course modifications are items, but they have additional
constraints beyond their normal item-ness.

Here's how to get different UUIDs for the same modification:

1. Alf and Barbie share a weekly event with no modifications
2. Alf changes the second occurrence's title.  There's nothing that
constrains the modification item's UUID, it's randomly generated
3. Simultaneously, Barbie changes the second occurrence's location.
Again, the modification she edits has a randomly generated UUID

When these get shared, we want the two modifications to merge.  Using
their arbitrary UUIDs would make that hard.

Sincerely,
Jeffrey