A few postings, here, here and here already talk about converting their blog urls into OpenID URLs. This method allows you to use your blog URI as your OpenID URI and login any one of the participating websites using that, as opposed to creating yet another user account on that website.
Those who already have an i-name (mine is http://xri.net/=rajeev.karamchedu) can use that instead. If you truly want a single URI, then why use a blog address ? The blog address is not permanent either. So instead of using the blog address, I created a forwarding service in my iname called (+openid) that will take me to my real open id
So my openid now is http://xri.net/=rajeev.karamchedu/(+openid)
A typical login process on a website then becomes:
- Supply your OpenID as http://xri.net/=<your iname>/(+openid) on the website (e.g. example.com)
- XRI.NET is contacted for a forwarding service, which then forwards to your OpenID server
- OpenID server authenticates example.com allowing you to control the duration of this authentication.
Using such an example, one can see that i-name framework complementing that of the OpenID. The thing that is bad about it is that I still have to create TWO accounts: One with the i-name service provider and another with an OpenID provider.
Can they not be the same ?