[cap-talk] capabilities are inherently multiuser things, correct?

[John Carlson]

It doesn't make any sense to have a single-user capability system,  
correct?  When I say single-user, I mean
no messages from the outside, and no requests going out across the  
internet, etc.  If capabilities are going
to be something, they've got to get out of the single-user mindset.

To me, this means having shared-capabilities, or communities formed  
on the internet.  How does one take
two or more communities, and form a single community, say one  
discussing approximate dynamic
programming (a cross-discipline idea based on decision making and  
optimization).  Does one have to
accept capabilities from all the other participants, or does one  
create a brand new community, and distribute
the capability to that community to everyone in the subcommunities.   
How do documents get moved between
communities?  Do you have to copy and paste, or do you generate new  
capabilities for all the documents
that you want to share between communities, and post the new  
capabilities to the entire new community.
What if you want to retain specific documents for just one  
discipline, on an unrelated topic.  Is there appropriate
filtering/search in capability systems?

Has this been discussed before?

John