Consider using claims defined in "OpenID Connect for Identity Assurance 1.0"

martin-lindstrom commented 1 year ago

OpenID Connect for Identity Assurance 1.0 defines some claims that we also are defining in our "Attribute Specification". These are:

place_of_birth - https://id.oidc.se/claim/placeOfbirth. A structured JSON object instead of our version that is a string.
birth_family_name, birth_given_name and birth_middle_name - Corresponding to "our" https://id.oidc.se/claim/birthName claim.

OpenID Connect for Identity Assurance 1.0 also defines the nationalities claim that is a string array representing the End-User's nationalities. We define a more generic country-claim, and we may want to remove that definition as well. However, there are more circumstances where we may want to represent a country other than to represent a nationality (in eIDAS for example).

I suggest that we remove our definitions (while still in draft mode).

leifj commented 1 year ago

Does it even make sense to focus our efforts on complex attributes that will be part of the wallet anyway?

martin-lindstrom commented 1 year ago

No, it doesn't. I was just given access to the PID Rule Book for the EUDI Wallet ecosystem, and when browsing it I see that we could get rid of some of our other "private" claims as well.

martin-lindstrom commented 7 months ago

We should not define any of the "general purpose claims". They just don't belong to our spec.

oidc-sweden / specifications

Consider using claims defined in "OpenID Connect for Identity Assurance 1.0" #63