[Cosmo-dev] cosmo 0.6.1 EIMML changes

[Jeffrey Harris]

Hi Randy,

> Just so we are clear:  If we have a "noteModificaiton" record type, its
> seems like we need everything in the "item" and "note" record types
> (plus recurrenceId and parentUuid) because a note modification can have
> a its own triageStatus, lastModifiedBy, displayName, etc.

I think if we're going to have parallel foo and fooModification records
for everything, probably we should have an ItemModification and a
NoteModification.

Alternately, we good do as I think bcm is suggesting, just add
parentUUID and recurrenceID as optional fields to pretty much every
record, and use their presence to distinguish between modifications and
normal items.

Or, if we didn't like having so many records and we didn't like having
recurrenceID in every record, we could go do what I originally thought
we were doing, having EventModification contain all of the fields in
Item and Note and Event, plus parentUUID and recurrenceID.

On a slightly different topic, since Morgen's proposing that
lastModifiedBy live in a separate record, not in Item or Note, we'll
need a lastModifiedByModification, too (or we could add parentUUID and
recurrenceID to this record as frequently-null record keys).

Sincerely,
Jeffrey