Douglas Otis wrote:
For clarity, OpenID Authentication 2.0 - Draft 11 4.1.1. Key-Value
Form Encoding should change to something like Keyword-Value Form
Encoding. Avoid using the word key to mean field or label. This
will cause confusion.
While I believe that key-value pairs is a
Johnny Bufu wrote:
I believe a key difference here is between what people would be
willing to do, and what people actually (will) do. For example:
- I would be willing to go to a rugby game, but I don't know if any
of my friends are going, so I probably won't go
- most of my friends
Johnny Bufu wrote:
These two seem to have been the rationale of the recent discussions
about splitting the OpenID spec into core/discovery/etc., which
seemed to make sense to a number of people (I'm just not sure if it's
worth / good tactical move at this stage).
I tend to think
On Sat, 2007-04-07 at 11:43 +0100, Martin Atkins wrote:
Douglas Otis wrote:
For clarity, OpenID Authentication 2.0 - Draft 11 4.1.1. Key-Value
Form Encoding should change to something like Keyword-Value Form
Encoding. Avoid using the word key to mean field or label. This
will
On Sat, 2007-04-07 at 08:58 -0700, Douglas Otis wrote:
Oops. I missed two references to keys.
---
4.1. Protocol Messages
The OpenID Authentication protocol messages are mappings of plain-text
labels to plain-text values. The labels and values permit the full
Unicode character set (UCS). When
On 4/7/07, Douglas Otis [EMAIL PROTECTED] wrote:
This would then require all locations that use the term key when
referring to a field label to be changed to label
-1
If it needs to be changed, Martin's suggestion of name instead is much better.
Josh
On Sat, 2007-04-07 at 10:30 -0700, Josh Hoyt wrote:
On 4/7/07, Douglas Otis [EMAIL PROTECTED] wrote:
This would then require all locations that use the term key when
referring to a field label to be changed to label
-1
If it needs to be changed, Martin's suggestion of name instead is
On Sat, 2007-04-07 at 18:22 -0700, Douglas Otis wrote:
Oops.
4.1. Protocol Messages (second paragraph)
Messages MUST NOT contain multiple values within the same field name.
Messages MUST NOT contain message parameters with the same field name.
-Doug
On 2-Apr-07, at 6:06 PM, Recordon, David wrote:
Sure, though I think there has also been a desire to do a bit of an
Are we in agreement then (about 1.0 and 1.1 sharing the same type URI)?
I went ahead and implemented SREG in openid4java, and exposed it in
such a way that the users won't
