[Openid-specs-ab] Final call for the determination of Google compatibility on the parameter names

[Mike Jones]

I think we should use consistent parameter names containing "openid2" for OpenID 2.0 specific values used in OpenID Connect transition data structures.  I'm fine documenting the Google values in an appendix but don't think they made the best name choices in some cases, and I don't think the standard should follow them verbatim.

                                                            -- Mike

From: openid-specs-ab-bounces at lists.openid.net [mailto:openid-specs-ab-bounces at lists.openid.net] On Behalf Of Justin Richer
Sent: Monday, July 14, 2014 6:41 PM
To: openid-specs-ab at lists.openid.net
Subject: Re: [Openid-specs-ab] Final call for the determination of Google compatibility on the parameter names

I would rather see consistency and clarity, especially if Google is the only large extant implementation of this.

 -- Justin

On 7/14/2014 7:55 PM, Nat Sakimura wrote:
Hi all:

This is the final call for the determination of whether we should align to Google for the parameter name or we should go for the consistency.

Please voice your opinion.

I will wait until the end of this week.

After this issue is closed, I will call for the WGLC to go to the implementer's draft vote.

--
Nat Sakimura (=nat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en




_______________________________________________

Openid-specs-ab mailing list

Openid-specs-ab at lists.openid.net<mailto:Openid-specs-ab at lists.openid.net>

http://lists.openid.net/mailman/listinfo/openid-specs-ab

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20140716/9c900190/attachment.html>