[cap-talk] User interface discussion, role based geometry editing

[John Carlson]

On Feb 25, 2008, at 9:56 PM, Jed Donnelley wrote:

> At 09:04 PM 2/25/2008, John Carlson wrote:
>> What is cap-talk's reaction to the use of roles when using a
>> collaborative geometry based application?  See:
>>
>> http://scitation.aip.org/getabs/servlet/GetabsServlet?prog=normal&id=JCISB6000006000001000002000001&idtype=cvips&gifs=yes
>> If this has been done for capabilities, can someone point me at it?
>
> Sorry, what is the "this" in the above?  Role-based access control?
> Role-based access control that is based on identities and allows
> changing roles would seem to depend on a notion of "who" such
> as that which Horton supplies.  Since there are no production
> Horton implementations (that I know of), I'd say its a pretty
> safe bet that role-based access control (particularly retroactive
> to role changes) hasn't been done with capabilities, whether
> for collaborative, geometry-based applications or not.

Of course I'm not asking if RBAC has been done with capabilities.  I'm  
asking if a collaborative geometry (CAD/Animation) application has  
been done with capabilities.  Say you're an engineering firm working  
on a complex project, and you want to distribute work to different  
firms, yet maintain as much control as possible of your project  
(perhaps by distributing images of the high level objects instead of  
the actual models).  Or say you're a movie production studio, and you  
want to distribute animation to several firms, but you don't want to  
give away the plot of the movie.  Or say you're an architectural firm,  
and you want to grant the ability for an interior design firm to  
populate the interior of your building without changing the structure.

Are these situations that neither role based nor capability security  
has a good answer for?

John