This is probably why the Social Graph Protocol normalizes everything to sgn:// URIs for canonicalization:<blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; "><p style="max-width: 65em; ">
The Social Graph Node Mapper is a community project to build a portable library to map social networking sites' URLs to and from a new canonical form (sgn:// URLs).</p></span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; "><p style="max-width: 65em; ">
For example, the following URLs are all the same person:</p></span></div></blockquote><div><meta charset="utf-8"><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; "><ul style="max-width: 65em; padding-left: 40px; ">
<ul><li><a href="http://brad.livejournal.com/" rel="nofollow" style="color: rgb(0, 0, 204); ">http://brad.livejournal.com/</a></li><li><a href="http://brad.livejournal.com/data/foaf" rel="nofollow" style="color: rgb(0, 0, 204); ">http://brad.livejournal.com/data/foaf</a></li>
<li><a href="http://brad.livejournal.com/data/rss" rel="nofollow" style="color: rgb(0, 0, 204); ">http://brad.livejournal.com/data/rss</a></li><li><a href="http://brad.livejournal.com/data/atom" rel="nofollow" style="color: rgb(0, 0, 204); ">http://brad.livejournal.com/data/atom</a></li>
<li><a href="http://brad.livejournal.com/profile" rel="nofollow" style="color: rgb(0, 0, 204); ">http://brad.livejournal.com/profile</a></li><li><a href="http://www.livejournal.com/userinfo.bml?user=brad" rel="nofollow" style="color: rgb(0, 0, 204); ">http://www.livejournal.com/userinfo.bml?user=brad</a></li>
<li>etc</li></ul></ul></span></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; "><p style="max-width: 65em; ">
With sgnodemapper, all of those would map to <strong>sgn://<a href="http://livejournal.com/?ident=brad">livejournal.com/?ident=brad</a></strong> . And then, from the sgn URL, you can map back to <tt style="font-size: 13px; ">http:// URLs</tt> for any known type: content page, profile page, RSS, Atom, etc.</p>
</span></div></blockquote><div><a href="http://code.google.com/apis/socialgraph/docs/canonical.html">http://code.google.com/apis/socialgraph/docs/canonical.html</a></div><div><a href="http://code.google.com/p/google-sgnodemapper/">http://code.google.com/p/google-sgnodemapper/</a></div>
<div><br></div><div>It's still domain-based identity, but it allows multiple representations of identifiers to be normalized more easily... this requires maintaining a huge mapping table, but attempts to be more pragmatic about the form of the identifier...<br>
<br><div class="gmail_quote">On Wed, Nov 3, 2010 at 8:32 AM, David Recordon <span dir="ltr"><<a href="mailto:recordond@gmail.com">recordond@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Spec draft is attached. As a side note, we should make sure that anything contributed to the Foundation's GitHub account is treated in the same manner as the Foundation's SVN server.<div><br></div><div>Agreed with John about this being bound to the domain.</div>
<div><br></div><div>I'm not convinced that splitting the id and domain is that much better than using an acct URI.</div><div><br></div><div>--David</div><div><br><div><br><div class="gmail_quote"><div><div></div><div class="h5">
On Wed, Nov 3, 2010 at 6:38 AM, Nat Sakimura <span dir="ltr"><<a href="mailto:sakimura@gmail.com" target="_blank">sakimura@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div class="h5">At the OpenID Summit, there were some discussion about how to uniquely identify the user. <div>
<br></div><div>There were some argument that it should user 'user_id' and 'domain'. </div>
<div>Upon some contemplation, I think we should use something like 'server_id' which is a unique identifier (perhaps domain, but maybe UUID etc.) instead of 'domain' as 'domain' may actually change. </div>
<div><br></div><div>What do you think? </div><div><br></div><div>P.S., David, could you just save your html connect proposal to a file and send it to this list? Then it will constitute the contribution and we can start discussion on that formally. Otherwise, we cannot from the IPR management point of view. <br clear="all">
<br>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/" target="_blank">http://www.sakimura.org/en/</a><br><a href="http://twitter.com/_nat_en" target="_blank">http://twitter.com/_nat_en</a><br>
</div>
<br></div></div><div class="im">_______________________________________________<br>
openid-specs-connect mailing list<br>
<a href="mailto:openid-specs-connect@lists.openid.net" target="_blank">openid-specs-connect@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-connect" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-connect</a><br>
<br></div></blockquote></div><br></div></div>
<br>_______________________________________________<br>
openid-specs-connect mailing list<br>
<a href="mailto:openid-specs-connect@lists.openid.net">openid-specs-connect@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-connect" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-connect</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Chris Messina <br>Open Web Advocate, Google <br><br>Web: <a href="http://factoryjoe.com">http://factoryjoe.com</a> <br>Follow me on Buzz: <a href="http://buzz.google.com/chrismessina">http://buzz.google.com/chrismessina</a> <br>
...or Twitter: <a href="http://twitter.com/chrismessina">http://twitter.com/chrismessina</a> <br><br>This email is: [ ] shareable [X] ask first [ ] private<br>I estimate the importance of this email to be: [ ] above average [X] average<br>
<br>
</div>