place_of_birth -> birthplace

Issue #1119 resolved
Travis Spencer created an issue

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)

  1. Michael Jones

    “birthplace” is shorter and an actual English word, so this seems like a reasonable change.

  2. Torsten Lodderstedt

    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?

  3. Torsten Lodderstedt

    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.

  4. Achim Schlosser

    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

  5. Achim Schlosser

    Putting it side by side (from the claims / evidence ticket) "claims":["birthdate","place_of_birth"] makes the point obvious

  6. Mark Haine

    Co-chairs decided that this should be closed for two reasons:

    1. this is a breaking change and there are implementations already
    2. there were no strong opions voiced at WG meetings

  7. Log in to comment