Email Address to URL Transformation

[Paul E. Jones]

Allen,

Perhaps we're in agreement, but I wasn't clear.

I think OpenID RPs should be able to use XRD documents in order to discover
the user's login service -- I like this.  What I would *not* want is for
that to be defined in this document:
http://yahoo.com/.well-known/host-meta

The reason is that this document is not user-specific and blankets
everything under the yahoo.com domain.

Rather, I'd want that to be in this document:
http://webfinger.yahooapis.com/?id={%id}

Or other document that allows the user to provide details about himself.
So, if I enter paulej at yahoo.com, RPs would still be directed to
http://openid.packetizer.com/paulej by querying the above document (or other
document) and finding some pointer to my OP.

Paul

> -----Original Message-----
> From: Allen Tom [mailto:atom at yahoo-inc.com]
> Sent: Monday, January 25, 2010 1:45 PM
> To: Paul E. Jones
> Cc: arshad.khan at channel321.com; specs at openid.net; 'John Panzer'
> Subject: Re: Email Address to URL Transformation
> 
> Hi Paul -
> 
> This assumes that every user with a Gmail or Yahoo email account can
> use
> their account as an OpenID. Simply asking the user to enter their email
> address to kickoff the sign-in process is a lot more scalable than the
> NASCAR, and is probably a lot more usable then asking them to enter
> their
> OpenID URL.
> 
> Allen
> 
> On 1/24/10 7:12 PM, "Paul E. Jones" <paulej at packetizer.com> wrote:
> 
> >
> > But, wouldn't that assume that every user who has a gmail.com or
> yahoo.com
> > email address uses Google or Yahoo, respectively, for OpenID?
> >
> >
>