Messages : 2.3.2. UserInfo Response Structure

[hideki nara]

This must be too minor and seems to be late. Curent JSON has only "address" claim as JSON object. But from the programmer's point of view, it would be easier to program if other claims would be contained in JSON objects which corresponds to OpenID Connect scopes.

I mean:

  { 
    "profile": {..},
    "email": {...},
    "address" : {...},
    "phone": {...}
  }

Regards.

[Former user]

For what it's worth, I actually rather like this suggestion.

The counter argument is likely to be "it's based off of Facebook and Facebook doesn't do it that way."

The counter-counter argument is "We already had VCard and PoCo and SCIM, do we need another arbitrary one?"

[Michael Jones]

This doesn't seem extensible to general claims. In what bucket would you put the favorite_color claim?

This just seems to add parsing complexity without a commensurate benefit.

The working group decided not to make this change.

[hideki nara]

Thank you very much. I got.

If possible, let me know the reason why the address claim is structured JSON object.
( Because I have not found any discussion log about this from the ML archive, but only "spec call notes" is found. )

Regards.