[OpenID] foaf and openid

[Boris Erdmann]

Well,

if we made

  http://mydoma.in/myfoaf.rdf

an OpenID2.0 consumer it could be accessed via

  http://mydoma.in/myfoaf.rdf?openid_identifier=your.open.id

and it would know how much foaf-data to reveal towards the requesting
identity. Not much protocol needed here to start with. (Thinking
further, this might be one of the first widely adopted use cases for
immediate Auth requests)

One would need to think about discovery (but see the sun article you
quoted, as this is the "officially" proposed method
http://www.foaf-project.org/2004/11/join.html). In an ideal world my
FOAF URL could be my OpenID, because every browser understands XSLT
and could render the foaf data into XHTML (but this would break simple
HTML discovery for OpenID). Or it could be done using Yadis.

Just a few thoughts... Is this approach too simple?

Boris



On 7/20/07, Story Henry <Henry.story at bblfish.net> wrote:
> Hi,
>
> It occurred to me recently that there was a nice and simple use of
> foaf and openid, where the two could be made to mesh very nicely and
> improove the user experience.
>
> http://blogs.sun.com/bblfish/entry/foaf_openid
>
> The idea is simply to add a foaf link to the html representations of
> the openid resource, so that servers could use that information to
> present more information to the client.
>
> Now a little more advanced question would be to specify for each
> service what type of depth of access one may want to give them to
> one's foaf file. This is where a little protocol tricks could come in
> useful.
>
> Henry
>
>
> _______________________________________________
> general mailing list
> general at openid.net
> http://openid.net/mailman/listinfo/general
>