<HTML>
<HEAD>
<TITLE>Re: Email Address to URL Transformation</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hi Paul -<BR>
<BR>
I’m not really a webfinger expert, however, the intent is to make it possible to decouple the user’s services from the user’s email provider, so they do not necessarily have to be the same entity.<BR>
<BR>
Allen<BR>
<BR>
<BR>
<BR>
On 1/27/10 1:18 PM, "Paul E. Jones" <<a href="paulej@packetizer.com">paulej@packetizer.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><FONT COLOR="#1F497D">George,<BR>
<BR>
You’re right that there are two things. The question is, do we wish to allow only OP advertisement via the host meta-data XRD file? That would certainly work for me. But, would users prefer to have a single email address (e.g., <a href="user@gmail.com">user@gmail.com</a>) and still be able to associate that with a different OP through webfinger?<BR>
<BR>
People could always have a different acct: URI. Is that preferred over trying to support both host meta-data and user meta-data XRD documents? <BR>
<BR>
Paul<BR>
<BR>
</FONT><BR>
</SPAN></FONT><FONT SIZE="2"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><B>From:</B> George Fletcher [<a href="mailto:gffletch@aol.com">mailto:gffletch@aol.com</a>] <BR>
<B>Sent:</B> Wednesday, January 27, 2010 3:11 PM<BR>
<B>To:</B> Paul E. Jones<BR>
<B>Cc:</B> 'Allen Tom'; <a href="arshad.khan@channel321.com">arshad.khan@channel321.com</a>; <a href="specs@openid.net">specs@openid.net</a><BR>
<B>Subject:</B> Re: Email Address to URL Transformation<BR>
</SPAN></FONT></FONT><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT><SPAN STYLE='font-size:12pt'><FONT FACE="Helvetica, Verdana, Arial">I think there are two different things being described... (1) meta data about the host (host-meta) and (2) meta data about the acct: identifier (XRD returned from the webfinger template URI endpoint).<BR>
<BR>
In this thread, that host-meta XRD only describes one service of the host... webfinger. However, there is nothing stopping the host from also adding a <Link> specifying that it is also an OpenID Provider. I agree with Allen that this is valuable information. This doesn't preclude or supersede the XRD returned for the user (based on the template URI endpoint).<BR>
<BR>
So, if an RP is looking to find the user's OP, then follow the webfinger protocol. If the RP just wants to know if a domain supports OpenID it can just look in the host-meta for that domain.<BR>
<BR>
I don't think they conflict.<BR>
<BR>
Thanks,<BR>
George<BR>
</FONT><FONT FACE="Times New Roman"><BR>
On 1/25/10 3:52 PM, Paul E. Jones wrote: <BR>
</FONT></SPAN><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Allen,<BR>
<BR>
Perhaps we're in agreement, but I wasn't clear.<BR>
<BR>
I think OpenID RPs should be able to use XRD documents in order to discover<BR>
the user's login service -- I like this. What I would *not* want is for<BR>
that to be defined in this document:<BR>
<a href="http://yahoo.com/.well-known/host-meta">http://yahoo.com/.well-known/host-meta</a><BR>
<BR>
The reason is that this document is not user-specific and blankets<BR>
everything under the yahoo.com domain.<BR>
<BR>
Rather, I'd want that to be in this document:<BR>
<a href="http://webfinger.yahooapis.com/?id={%id}">http://webfinger.yahooapis.com/?id={%id}</a><BR>
<BR>
Or other document that allows the user to provide details about himself.<BR>
So, if I enter <a href="paulej@yahoo.com">paulej@yahoo.com</a>, RPs would still be directed to<BR>
<a href="http://openid.packetizer.com/paulej">http://openid.packetizer.com/paulej</a> by querying the above document (or other<BR>
document) and finding some pointer to my OP.<BR>
<BR>
Paul<BR>
<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>-----Original Message-----<BR>
From: Allen Tom [<a href="mailto:atom@yahoo-inc.com">mailto:atom@yahoo-inc.com</a>]<BR>
Sent: Monday, January 25, 2010 1:45 PM<BR>
To: Paul E. Jones<BR>
Cc: <a href="arshad.khan@channel321.com">arshad.khan@channel321.com</a>; <a href="specs@openid.net">specs@openid.net</a>; 'John Panzer'<BR>
Subject: Re: Email Address to URL Transformation<BR>
<BR>
Hi Paul -<BR>
<BR>
This assumes that every user with a Gmail or Yahoo email account can<BR>
use<BR>
their account as an OpenID. Simply asking the user to enter their email<BR>
address to kickoff the sign-in process is a lot more scalable than the<BR>
NASCAR, and is probably a lot more usable then asking them to enter<BR>
their<BR>
OpenID URL.<BR>
<BR>
Allen<BR>
<BR>
On 1/24/10 7:12 PM, "Paul E. Jones" <<a href="paulej@packetizer.com">paulej@packetizer.com</a>> <<a href="mailto:paulej@packetizer.com">mailto:paulej@packetizer.com</a>> wrote:<BR>
<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
But, wouldn't that assume that every user who has a gmail.com or<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>yahoo.com<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>email address uses Google or Yahoo, respectively, for OpenID?<BR>
<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
<BR>
_______________________________________________<BR>
specs mailing list<BR>
<a href="specs@lists.openid.net">specs@lists.openid.net</a><BR>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs">http://lists.openid.net/mailman/listinfo/openid-specs</a><BR>
<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>