On Thu, Oct 30, 2008 at 1:13 PM, Steven Livingstone-Perez <span dir="ltr"><<a href="mailto:weblivz@hotmail.com">weblivz@hotmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I saw that coming Ben and it's a fair point.<br>
<br>
When I do consultancy with various places they give me an email.<br>
<br>
I may share that email with their systems that require an OpenID - but I'd<br>
rather tie it to my independent OpenID. That way, if I register with a<br>
system that continues to be valuable to me when I leave that company<br>
(government systems being a good example) I can simply change the email but<br>
maintain my identity.<br>
<br>
Of course you may argue why not change the identity to the new email rather<br>
then? I just don't like changing primary identifiers in this manner due to<br>
side effects in other systems etc.<br>
<div><div></div><div class="Wj3C7c"><br>
</div></div></blockquote></div><br>I agree. It may not be a good assumption, but my impression is that my OpenID (<a href="http://openid.sappenin.com">http://openid.sappenin.com</a>) is going to be "under my control" and "appropriate to use" for a much longer time than my common email addresses (<a href="mailto:something@gmail.com">something@gmail.com</a>, <a href="mailto:somethingelse@yahoo.com">somethingelse@yahoo.com</a>, <a href="mailto:personal@sappenin.com">personal@sappenin.com</a>, etc) because it makes sense to use different email addresses throughout my day, year, and life -- whereas I forsee being able to use the same OpenID URL forever (as long as <a href="http://sappenin.com">sappenin.com</a> is around, at least). In my opinion, one more reason (user convenience) to just map an email address to an OpenID (XRI or URL).<br>