- changed component to Assurance
place_of_birth -> birthplace
Section 3.1 of the identity assurance draft spec defines a new claim called place_of_birth
. This would be more natural if renamed to birthplace (one word).
Comments (17)
-
reporter -
“birthplace” is shorter and an actual English word, so this seems like a reasonable change.
-
I agree, this makes sense to me
-
-
assigned issue to
-
assigned issue to
-
@Torsten Lodderstedt I created a pull request #3 for this purpose. If the WG accepts the change, please review the pull request and merge it if it is okay.
-
- changed status to open
PR exists
-
Note: this is a breaking change. Is it worth the impact for existing implementations? If so, how do we support existing implementations in the migration process? Or shall we enable OPs to support different versions of our spec?
-
I personally have no strong opinion as to whether the claim name should be changed to
birthplace
or not although I have submitted the pull request #3. -
Discussion in the call today:
- place of birth is the term used in ICAO 93.3 (part 3), which is the international standard for travel/id documents. That’s a good reason to stick to place_of_birth
- If we nevertheless decide, we need a version management concept, since this a breaking change.
-
Revisiting this after the call - a good argument why this should be changed:
- ICAO 93.3 (part 3) does use the wording “Place of birth“, having that said ICAO 93.3 also uses “Date of birth“ in its definition.
- OIDC core (https://openid.net/specs/openid-connect-core-1_0.html#ClaimsContents) defines birthdate instead of “Date of birth“ (which poses a similar question)
- From an OIDC perspective the use of birthplace seems to the sensible choice in term of consistency of the overall specification, using a different “syntax“ here looks rather strange
-
Putting it side by side (from the claims / evidence ticket)
"claims":["birthdate","place_of_birth"]
makes the point obvious -
- changed milestone to Implementer's Draft 2
- removed component
-
- removed milestone
-
- changed milestone to next stage
-
- changed milestone to next stage (candidates)
-
Co-chairs decided that this should be closed for two reasons:
- this is a breaking change and there are implementations already
- there were no strong opions voiced at WG meetings
-
- changed status to resolved
reasons noted in comments section
- Log in to comment