[Cosmo-dev] more fun with items in multiple collections

[Jeffrey Harris]

>> 1. I share collection A with item C read-only.
>> 2. Joe Blow subscribes to A and gets C read-only.
>> 3. Joe uses eimml to create shared collection B containing C read-write
>> and is able to update C.
>>
>> It seems like this is undesirable and we need to prevent this from
>> happening.
> 
> i remember walking around downtown portland on an extremely hot day
> last summer discussing this very thing with jeffrey and bobby. we
> didn't have any solutions then either ;)

Yup, this is really tough.

We're never going to really solve this (examples get worse when you
throw multiple Cosmo instances in the mix) without an
ownership/signature model for items, which is an interesting idea and
doesn't seem impossible but is way, way, way out of scope for now.  The
user workflows are really involved, I think.

I thought our last rough conversations about this pointed us towards
scoping items per-user, with the possibility of linking some items in
one user's account to items in another user's account if the appropriate
permissions existed?  I'm just hand-waving here, but that seemed
reasonably stable to me.

Sincerely,
Jeffrey