Mailing-List: contact clerezza-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: clerezza-dev@incubator.apache.org
Date: Sat, 28 May 2011 12:50:47 +0000 (UTC)
From: "Henry Story (JIRA)" <jira@apache.org>
To: clerezza-dev@incubator.apache.org
Message-ID: 
 <551367545.50812.1306587047352.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <559935087.6286.1305189347459.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CLEREZZA-515) ugly account name when logging
 into ZZ with a foreign WebID
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLEREZZA-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040589#comment-13040589 ] 

Henry Story commented on CLEREZZA-515:
--------------------------------------

Reverted changes, though will keep them on the bblfish branch, as I have not seen any good reasons against them.

The ugliness problem was dealt with in depth here. The issue of what it looks like on the user front page was just one symptom of the problem of forcing usernames as identifiers of a person when no such identifier is needed, such as for WebID logged in users, or perhaps even OpenID logged in users. 

This is not a criticism of the initial decision to use account names, btw. That was a good expedient to get things and see how things were working. But we might as well move to the next stage which this patch was about. What did it do:

  Currently the system graph contains statements like this:

_:anon    a       <http://xmlns.com/foaf/0.1/Agent> ;
      <http://clerezza.org/2009/08/platform#userName>
              "anonymous" .

:joe    a       <http://xmlns.com/foaf/0.1/Agent> ;
         <http://clerezza.org/2009/08/platform#userName>
              "joe" .

   This patch allowed statements like this:

<http://bblfish.net/#hjs> a foaf:Agent .

ie without the need to create an arbitrary zz:userName .

The handle of the agent should be _:anon, :joe and  <http://bblfish.net/#hjs> . 

This make it possible then to have people authenticate with OpenID, and then add the following
to the system graph.

  _:somone foaf:openid <http://openid.org/joe> .

Or using fingerpoint with

 _:someone foaf:openid <accnt:henry.story@gmail.com> .

Given the openid is really designed for humans more than robots, it makes more sense to give users that authenticate that way an account. But it is clear that it would be preferable to do that AFTER the user has authenticated, and perhaps had a bit of fun on the site, at which point he can decide what kind of account name he would like to have, and simply add the relation

  _:somone zz:accountName "joe" .

As I was a bit in a hurry to get this out for the Identity in the browser Workshop in California - the presentation is online here http://bblfish.net/blog/2011/05/25/ - I probably did not go into enough explanation of what this patch was doing, and understand that it may on first look have seemed somewhat larger answer to the problem than might have seemed necessary. But on closer inspection I am sure others here will agree that the general gist of this is the right solution, and one that Clerezza being a semantic web engine is in an excellent position to enable - I can see that making this possible in SQL or imap environments would be a lot more difficult.

Of course there can be improvements to the way things are being done here, and I will be working on some of them on my branch.


> ugly account name when logging into ZZ with a foreign WebID
> -----------------------------------------------------------
>
>                 Key: CLEREZZA-515
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-515
>             Project: Clerezza
>          Issue Type: Bug
>            Reporter: Henry Story
>
> When loggin in with my WebID http://bblfish.net/people/henry/card#me I get a login name
>      http___bblfish.net_people_henry_card_me
> that is really ugly, and does not fit on the top page.  It is not even guaranteed to be unique, so that it could
> lead to acces control issues.
>    The server should try to display a name that is good looking, perhaps the person first name, last name, or 
> nickname found in the profile document.  What if none of those exist? Would a short automatically created name
> not be better? Any ideas?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira