<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
John Panzer wrote:
<blockquote cite="mid:48F4E399.2040602@acm.org" type="cite">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<br>
I can also think of #4: I have existing legacy systems that are based
on having the verified email address (especially as a foreign key), and
want to migrate incrementally, if at all.<br>
</blockquote>
<br>
Bingo! <br>
<br>
Sites need to have a realistic migration path to OpenID. Many sites
have registration systems keyed off of the user's verified email
address, and they'd probably want to minimize the changes in their
backend systems to support OpenID. <br>
<br>
I do think that URL based identifiers are ideal, however it seems that
RPs may want an even lighter weight way to start using OpenID, so
defining a use case for Email Verification could be a way to transition
RPs to OpenID.<br>
<br>
Allen<br>
<br>
<br>
<br>
</body>
</html>