We had been calling a kind that could be mixed-in an "aspect" but that's a term already used in the repository for metadata about an attribute (e.g its cardinality). We dubbed these things "Mixin kinds" instead -- event, task and email are mixin kinds because they are designed to be added/stamped to other items.
We noted that mixin kinds are not necessarily limited to Content Items. There may be a need to have mixin kinds for blocks, for example.
For now, we will attempt to use Morgen's parcel support for clouds, and define clouds for at least email, task and event. We could also try to do so for stamped TaskEvent? and other composite kinds.
Issues to resolve:
Whether unstamp/restamp works the same way as undo/redo (need to talk to Mimi).
LATER: Mimi said they don't work the same way, which agreed with our assumptions.
Whether unstamp/restamp support (remembering the attribute values at unstamp so you can reuse them at restamp time) is on the schedule for 0.4. Need to confirm with Katie and Chao.
We'd like to confirm with Mimi the model for "do-by" as well as "due date" and what that means for the stamping model, and whether this will be too confusing
We still have a great deal of uncertainty about whether each Content Item has only one item cloud, or many. On the one hand, the user would like to know what a Content Item includes (and does not include) without having that change depending on what function is used. OTOH, multiple item clouds definitely provides flexibility to do things that users want like filtering email addresses out of emails when sharing them.