As currently defined, an extension has a global namespace URI as well as
a request-local alias/prefix. For an extension with the namespace
http://example.com/blah that has a field "foo", the following fields are
to be sent:
openid.ns.blah=http://example.com/blah
openid.blah.foo=bar
As the author of consumers I have never seen the point of 2.0
Yadis and XRDS in 1.1 was welcome and a great improvement over , but
XRI seems like something evil to me. Yes, 2.0 is about more than XRI, but
on the usage end, at least for my apps, there's not much difference.
I use the JanRain libra
Cool, thanks!
> -Original Message-
> From: Johnny Bufu [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 30, 2007 9:51 AM
> To: Granqvist, Hans
> Cc: OpenID specs list
> Subject: Re: encoding newlines in attribute values
>
> Hans,
>
> On 30-Apr-07, at 9:22 AM, Granqvist, Hans wrote:
> >
All,
Over the last several weeks, I have tried [1][2] to ask
the list to clarify into the state of the current OpenID
2.0 specification draft.
There seems to be little interest in finalizing 2.0. The
current draft 11 is over three months old. Draft 5 dates
back over ten months, and who knows
Hans,
On 30-Apr-07, at 9:22 AM, Granqvist, Hans wrote:
> Just so we're all on the same page: Can you post a link
> to the referenced proposal?
Mark has announced it here on the list:
http://openid.net/pipermail/specs/2007-April/001630.html
Johnny
_
Hi Johnny,
Just so we're all on the same page: Can you post a link
to the referenced proposal?
Thanks,
Hans
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Johnny Bufu
> Sent: Friday, April 27, 2007 3:46 PM
> To: OpenID specs list
> Subject: Re:
