<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
I played with web identity, in a blog post. I feel like I'm close to what was originally intended, with the XRI/XDI/HXRN and openid integration.<BR> <BR>But, is this REALLY what folks intended? I cannot decide it its nirvana, or a giant mess.<BR> <BR>if it is close to what was sought after, Im thinking of going a last step: ensuring a missing piece from the XRI trusted reoslution is replicated using present day mechanism - delivering the ability of one namespace to sign the next, in a chain, supproting a list of of XRDs in an XRDS. Rather than do it the (unwanted) XRI trusted resolution way and use XRDS chains (great idea, wrong timing), Ill just use cross-certificates, which are now mainstream (for name space co-recognition, purposes)<BR> <BR> <BR><div>> From: home_pw@msn.com<br>> To: openid-general@lists.openid.net<br>> Date: Fri, 23 Dec 2011 13:08:12 -0800<br>> Subject: Re: [OpenID] putting myopenid clients certs together with openid foundation enrollment, with webid profiles<br>> <br>> <br>> i didnt get anywhere with myopenid (and its client certs with https capability).<br>> <br>> <br>> <br>> But we did the experiment in the webid project (instead). I wrote it up here : http://yorkporc.wordpress.com/2011/12/23/testing-openid-and-webid-together/<br>> <br>> <br>> <br>> Rather than competing with openid, I now cleary see how webid is complementing and adding some value. <br>> <br>> <br>> <br>> <br>> _______________________________________________<br>> general mailing list<br>> general@lists.openid.net<br>> http://lists.openid.net/mailman/listinfo/openid-general<br></div> </div></body>
</html>