Consider recommending a way to encode other data types.

[danielfett]

The spec should define a way to support other data types. Pictures of the credential holders will be a common case, but other data types might occur as well.

OpenID Connect already defines a claim:

picture string URL of the End-User's profile picture. This URL MUST refer to an image file (for example, a PNG, JPEG, or GIF image file), rather than to a Web page containing an image.

In that sense, we could just recommend that data types other than the native JSON types should be encoded, for example, as data URIs (that would be compatible to the definition of picture above).

[babisRoutis]

Hi @danielfett

I find your proposal really useful.

"Data URIs" are those described in RFC2397 ?

[awoie]

I'm supportive of this approach as well.