There seems to be a misunderstanding here, I think the user admin shall support all 3 options. On one hand we don't always know about existing WebId of the users, if we assign a Uri and later the user discloses her WebId we have troublesome owl:sameAs URIs. Dealing with bnodes is much less troubles than having many names and having to deal with a local and a remote profile.
Cheers, reto On Tue, Oct 19, 2010 at 9:16 AM, Oliver Strässer < [email protected]> wrote: > I think a merge of option one and to will be good. > if the admin, who create the user, enter an uri, this uri will be used. if > no uri will be entered, the system generates a random web ID. > > if users aren't bnodes, the creator predicate could be in another graph, as > the system or content graph. > > cheers > oli > > -----Ursprüngliche Nachricht----- > Von: Reto Bachmann-Gmuer [mailto:[email protected]] > Gesendet: Montag, 18. Oktober 2010 23:03 > An: Manuel Innerhofer > Cc: [email protected] > Betreff: Re: Users as UriRefs instead of BNodes > > Hi Manuel > > I think in the UserManager this could be an option, but should not be the > default. You should have 3 Options > > 1. Automatically Assign uri => The users get a WebId on the instance > 2. Enter Uri => For adding Users of which you know an existing WebId > 3. BNode => So the User can either create a local WebId or connect to an > existing one > > Cheers, > reto > > > On Mon, Oct 18, 2010 at 4:26 PM, Manuel Innerhofer <[email protected] > >wrote: > > > Hi Reto, > > > > We want to replace the user BNodes with UriRefs for our CMS. The problem > is > > that new users created by the user manager are still BNodes. Could I also > > modify the usermanager to create users with UriRefs? > > > > Regards, > > Manuel > > > > > > >
