W3C home > Mailing lists > Public > public-xg-webid@w3.org > September 2011

OpenId, WebID, BrowserId & WebFinger

From: Henry Story <henry.story@bblfish.net>
Date: Sat, 24 Sep 2011 11:31:21 +0200
Message-Id: <F0A11642-81B5-48FA-B609-291E43746704@bblfish.net>
To: WebID XG <public-xg-webid@w3.org>
Here on G+ someone asked about the relationship between these 3 standards [1]. My answer was the following:

<blockquote>
WebFinger does not do Authentication, it ties an e-mail address to a profile. As a result it allows OpenId to use e-mail addresses as identifiers. If you want a detailed information on http://webid.info/ compared to BrowserId then you can check out http://security.stackexchange.com/questions/5406/what-are-the-main-advantages-and-disadvantages-of-webid-compared-to-browserid/5424 . They can all tie together quite easily in fact. It's just that WebID uses tools that work in the browser now ( if they support TLS) OpenId uses protocols that all browsers must support (even if they don't have TLS) and BrowserId is trying to make crypto independent of TLS - which means it will be a while before it works independently of their browser.
</blockquote>

In any case perhaps that helps make something clear, and could be added to the FAQ.

Anything to add?

Henry

[1] perhaps it is world readable (not sure)
    https://plus.google.com/110908828231461227679/posts/TLPmqEfwSLz


Social Web Architect
http://bblfish.net/
Received on Saturday, 24 September 2011 09:32:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 24 September 2011 09:32:02 GMT