Isn't this a case where the Yadis infrastructure should be used instead of Yet Another Link Tag?

On Oct 19, 2006, at 8:21, Drummond Reed wrote:

Martin, I agree with Dick, this is a fascinating idea. P3P had the same idea notion for a site advertising the location of the P3P privacy policy: it defined a standard HTML/XHTML link tag that could be put on any page of a site that told the browser where to locate the P3P policy document for the
site (or for any portion of the site).

        http://www.w3.org/TR/P3P/#ref_syntax

Are you proposing the same thing for OpenID login?

(Kewl!)

=Drummond

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Dick Hardt
Sent: Thursday, October 19, 2006 12:53 AM
To: Martin Atkins
Cc: specs@openid.net
Subject: Re: PROPOSAL: OpenID Form Clarification (A.4)


On 19-Oct-06, at 12:35 AM, Martin Atkins wrote:

Dick Hardt wrote:

In order for the RUA to detect that a site supports OpenID, it sees a form with a single input with a "name" of openid_identiifier. The RUA
can then look at the action and post the data directly to the RP.


I think it'd be better to implement this as either a META or a LINK
element alongside a standard protocol for communicating with the
nominated URL.

This way the site can declare on *all pages*, rather than on the
forms-based login page, that it accepts OpenID auth. This allows the
user to go to the RP's home page (or any other page) and click the
"OpenID Login" button on the browser's toolbar and have it work.

That is an interesting idea. Would you like to take a stab at more
specifics?

-- Dick
_______________________________________________
specs mailing list
specs@openid.net
http://openid.net/mailman/listinfo/specs

_______________________________________________
specs mailing list
specs@openid.net
http://openid.net/mailman/listinfo/specs

Johannes Ernst
NetMesh Inc.

GIF image

 http://netmesh.info/jernst




_______________________________________________
specs mailing list
specs@openid.net
http://openid.net/mailman/listinfo/specs

Reply via email to