IMO 99% of the users (of an application based on apache clerezza) has no idea what an openid or webid is. the users are not ready yet for such cutting-edge technologies so we have to hide it. The dilemma is they have to use custom applications developed by third party company.
On Tue, Oct 19, 2010 at 1:57 PM, Reto Bachmann-Gmuer <[email protected]> wrote: > On Tue, Oct 19, 2010 at 11:51 AM, Tsuyoshi Ito <[email protected]> wrote: > >> On Tue, Oct 19, 2010 at 11:25 AM, Reto Bachmann-Gmuer >> <[email protected]> wrote: >> > On Tue, Oct 19, 2010 at 10:24 AM, Tsuyoshi Ito <[email protected]> >> wrote: >> > >> >> Users as BNodes are very troublesome in the daily business especially >> >> if apps using their own graphs. I know in theory it makes sense to >> >> have users as BNodes but i suggest not to use users as BNodes in >> >> praxis. >> >> >> > I think its completely ok not to offer some functionality to users as >> long >> > as they don't have a WebId, this is what is currently done (without >> WebId >> > no user graphs). >> >> Missunderstanding, try to explain it: Developers creating apps. these >> apps associate users with content in their own graphs therefore a >> BNode with the necessary data of a user has to be stored in the app >> graph. Methods have to be implemented to retrieve users and associate >> them with the system graph users. This procedure is error-prone. >> >> Therefore I suggest not to use Bnodes as default option because it >> makes the live a lot easier for the developers. >> > I see this, this is why I suggest the application makes its functionality > depending on the availability of a URI for the user. If a User without URI > attempts to use the application she can either create a new WebId or connect > with her existing WebId/OpenId (of course the application has just to > redirect to the profile page). > > Cheers, > reto > -- --trialox ag-------------------------------------- Tsuyoshi Ito Binzmuehlestrasse 14 CH-8050 Zürich Tel. +41 44 635 75 77 URL: http://trialox.org
