On 1/30/07, Josh Hoyt [EMAIL PROTECTED] wrote:
*snip*
While it is true that since the link relationship names changed, the
openid2 is technically redundant, I think it is much clearer to
everybody what is going on if the link relationship contains the
version number. If the protocol version
I'm happy changing it from AJAX. I think it was originally used since
AJAX is a bit overloaded already and people normally understand the
flashy non-reloading sort of thing when saying it.
--David
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Rowan
On 1/9/07, Johnny Bufu [EMAIL PROTECTED] wrote:
Please have a look at the latest (draft 4) OpenID Attribute Exchange
1.0 specification:
http://openid.net/specs/openid-attribute-exchange-1_0-04.html
This is looking good. I've been going over it updating my drupal
modules to draft 4.
The
On 1/31/07, Recordon, David [EMAIL PROTECTED] wrote:
I'm happy changing it from AJAX. I think it was originally used since
AJAX is a bit overloaded already and people normally understand the
flashy non-reloading sort of thing when saying it.
I suppose some people might, but for a developer
Supporting point 2 (user with a v1 OP and a *separate* v2 OP) seems a bit
unnecessary. A single OP can support v1 and v2 RPs at the same time. Point 2 is
the sort of corner-case that can be supported by a yardis file, but needn’t be
supported by the simple HTML discovery alternative.
My vote
Hi Rowan,
On 31-Jan-07, at 1:26 PM, Rowan Kerr wrote:
On 1/9/07, Johnny Bufu [EMAIL PROTECTED] wrote:
Please have a look at the latest (draft 4) OpenID Attribute Exchange
1.0 specification:
http://openid.net/specs/openid-attribute-exchange-1_0-04.html
This is looking good. I've been going
