[Cosmo-dev] cosmo 0.6.1 EIMML changes

[Jeffrey Harris]

Hi Randy,

> Yeah what about making the UUID of a mod be a composition of parentUuid
> and recurrenceId instead of a random UUID?

Grant and I have discussed doing this internally in Chandler several
times, and have always come around to it not working very well for
Chandler internal UUIDs.  But just because it works out poorly in
Chandler doesn't mean we couldn't serialize modifications that way.

It's a bummer that we miscommunicated about all this, I've implemented
one thing in Chandler, you've implemented a different thing in Cosmo, we
both thought we were working from the same page.  I'm not sure which
side will have an easier time shifting, but I can certainly work on
changing Chandler's implementation.

I can change Chandler's modification translators to whatever works best
for Cosmo, as long as somehow, any record associated with a modification
includes an indication that it's about a modification and what that
modification's recurrence-id is.

Sincerely,
Jeffrey