Hi Senaka, I am bit confused about the requirement. Which one is it?
a) Is it not to have ownership with one user, so multiple users own it so if one user left, still document is accessible b) Is it we want to give Read, Write, Delete permissions to users? (We had this long time ago, did we loose that with role based mode) Could u give an example? --Srinath On Wed, Jul 24, 2013 at 2:37 PM, Amila Suriarachchi <am...@wso2.com> wrote: > > > > On Tue, Jul 23, 2013 at 2:17 PM, Senaka Fernando <sen...@wso2.com> wrote: > >> Hi all, >> >> This is WRT, #1725 on Redmine. >> >> +++++++++++++++++++++ >> The idea is to create a special role that gives READ, WRITE, DELETE and >> AUTHORIZE access to a particular asset making it possible for a particular >> user or set of users take ownership of it. This thought came up during a >> WSO2 Store Milestone Planning Meeting, and mimics the functionality of >> Google Docs. >> +++++++++++++++++++++ >> > > I think first you need to think whether this is a problem we should try to > solve with a role based model. When we say role it represent a set of > permissions which are belongs to a meaning full actor in a system. Here we > are going to define roles per resource. But this seems to be a problem to > solve with direct user permission assignment. > > thanks, > Amila. > > >> >> Before going ahead with this, we have a few things to get clarified. >> >> 1. How would this role be named? This shouldn't be the name of the Asset >> itself, because there can be multiple assets by the same name. It even cant >> be name + namespace (or similar prefix/postfix), because there can be >> assets that differ by version. So, what's the best way to name it? >> >> 2. How should we be displaying this role in the management console? >> Should it show up just like any other role, or is there some special >> treatment in the Registry Browser? Since the role and the asset are 1-to-1, >> we shouldn't be displaying such roles against other assets, which makes it >> require some special treatment. >> >> 3. Is it just one such role or more? For instance, G-Docs has three types >> of privileges when it comes to sharing (i.e. View, Edit, Owner). >> >> Appreciate some quick responses on these in order to make it possible for >> us to ship this with G-Reg 4.6.0, making it available for WSO2 Store etc. >> >> Thanks, >> Senaka. >> >> -- >> * <http://us13.wso2con.com/> >> * >> * >> * >> *Senaka Fernando* >> Senior Technical Lead; WSO2 Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Amila Suriarachchi* > > Software Architect > WSO2 Inc. ; http://wso2.com > lean . enterprise . middleware > > phone : +94 71 3082805 > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- ============================ Srinath Perera, Ph.D. http://people.apache.org/~hemapani/ http://srinathsview.blogspot.com/
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
