[Openid-specs-ab] Two questions for today's call

Mike Jones Michael.Jones at microsoft.com
Thu Jun 30 21:00:10 UTC 2011


1.  Locale:

The definition of locale in the UserInfo spec<http://openid.net/specs/openid-connect-userinfo-1_0.html> is currently:
The user's locale, represented as an ISO 639-1 Alpha-2 [ISO639‑1] language code in lowercase and ISO 3166-1 Alpha-2 [ISO3166‑1] Country Code in uppercase, separated by an underscore. For example, "en_US" or "fr_CA".

This is based upon the Facebook usage.  A better thing to do would probably be to use RFC 5646<http://tools.ietf.org/html/rfc5646>, where these names would be “en-US” and “fr-CA”, and where scripts can also be represented when necessary.  I’m prone to change to RFC 5646 and put a compatibility note in saying that some IdPs may use underscores rather than dashes between the language and country parts.

2.  Request parameter inconsistency between Framework and HTTP-Redirect specs:

The HTTP-redirect spec<http://openid.net/specs/openid-connect-http-redirect-1_0.html> includes this portion of an example in 3.1.1.2:
   "ses":
      {
        "mxa": 86400,
        "eaa": 2
      }
Whereas, the Framework spec<http://openid.net/specs/openid-connect-framework-1_0.html> includes this portion of an example in 3.1.1:

    "idt":

      {

        "clm":

          {

           "aat": null

          }

        "mxa": 86400,

        "eaa": 2

      }
Which is right?

                                                            -- Mike


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20110630/96fb2542/attachment.html>


More information about the Openid-specs-ab mailing list