[OpenID-Specs-eKYC-IDA] [EXTERNAL] Re: place_of_birth vs. birthplace

Wed Feb 19 17:10:04 UTC 2020

I really think that the fields need to be more prescriptive in the format and encoding , the ISO mDL table does a real goo job of this

Table 3 (continued)

Identifier

Name

Definition

Presence

Field

format

Encoding

issue_date

Date of Issue

Date licence document was issued

M

full-date or date- time

tdate or

#6.18013(tstr)

expiry_date

Date of Expiry

Date licence document expires

M

full-date or date- time

tdate or

#6.18013(tstr)

issuing_coun- try

Issuing country

country code as alpha 2 code, defined in

ISO 3166-1, which issued the mDL or within

which the licensing authority is located

M

F2A

tstr

issuing_au- thority

Issuing authority

Name of licensing authority, or issuing country if separate licensing authorities have not been authorized. See 7. 4.3.

M

V65ANS

tstr

document_

number

Licence number

The number assigned or calculated by the issuing authority

M

V25AN

tstr

administra-

tive_number

Administrative number

An audit control number assigned by the licensing authority

O

V25ANS

tstr

driving_privi- leges

Categories of vehi- cles/ restrictions/ conditions

Driving privileges the licence holder is authorized to drive. It consists of category issue date, expiry date, restriction/condi- tion sign code, restriction/condition sign and restriction/condition value. See 7.4.4.

M

See 7.4.4

See 7.4.4.

un_distin- guishing_sign

UN distinguishing sign

Distinguishing sign of the issuing country according to 18013-1 annex F

NOTE  this field is added for purposes of

the UN conventions on driving licences

R

N/A

tstr

gender

Gender

Licence holder’s gender: M for male, F for

female, X for not specified

O

F1A

tstr

height

Height (cm) a

Licence holder’s height in centimetres

O

F3N

uint

weight

Weight (kg) a

Licence holder’s weight in kilograms

O

F3N

uint

eye_color

Eye colour

Licence holder’s eye colour: blue, brown, black, hazel, green, grey, pink, dichromatic

O

V12A

tstr

hair_color

Hair colour

Licence holder’s hair colour: brown, black,

blonde, grey, red, auburn, sandy, white, bald

O

V12A

tstr

birth_place

Place of birth

Country and municipality or state/prov- ince where the licence holder was born

O

V33A

tstr

resident_ad- dress

Permanent place of residence

The place where the licence holder resides and/or may be contacted (street/house number, municipality etc.)

O

V108ANS

tstr

portrait

Portrait of mDL Holder

A reproduction of the licence holder’s por- trait. See 7. 4.2.

M

N/A

bstr

portrait_cap- ture_date

Portrait image timestamp

Date when picture was taken

O

date- time

tdate

age_in_years

Age attestation: How

old are you (in years)?

The age of the mDL Holder

O

V3N

uint

age_birth_ year

Age attestation: In what year were you born?

The year when the mDL Holder was born

O

F4N

uint

age_over_NN

Age attestation: Nearest “true” attes- tation above request

See 7. 4.5

O

N/A

bool

issuing_juris- diction

Issuing jurisdiction

Country subdivision code as defined in clause 8, ISO 3166-2. The first part of the code shall be the same as the value for issu- ing_country. This element is intended to be used in cases where the issuing jurisdiction is different from the issuing authority.

O

N/A

tstr

Table 3 (continued)

Identifier

Name

Definition

Presence

Field

format

Encoding

nationality

Nationality

Nationality of the mDL Holder as two letter country code (alpha-2 code) defined in ISO 3166-1

O

F2A

tstr

resident_city

Resident city

The city where the mDL Holder lives

O

ANS

tstr

resident_state

Resident state/prov- ince/district

The state/province/district where the mDL Holder lives

O

ANS

tstr

resident_ postal_code

Resident postal code

The postal code of the mDL Holder

O

ANS

tstr

biometric_ template_xx

Biometric template XX

See 7. 4.6

O

N/A

bstr

name_nation- al_character

Full name of holder in full UTF-8 character set

The full name of the mDL Holder in his/her national characters

O

N/A

tstr

signature_ usual_mark

Signature / usual mark

Image of the signature or usual mark of the mDL Holder

O

See 7. 4.7

See 7. 4.7

online_token_ xxxx

Online token

See 7. 4.8

O

N/A

tstr

online_url_ xxxx

Online URL

See 7. 4.8

O

N/A

tstr

Key

Presence:

M/R/O: The presence is mandatory (M), recommended (R) or optional (O)

Field format:

A: alphabetic character, hexadecimal ranges '41' – '5A' (Latin capital letters), '61' – '7A' (Latin small letters), 'C0' – 'D6', 'D8'

– 'F6' and 'F8' – 'FF' of ISO/IEC 8859-1

N: numeric character, hexadecimal range '30' – '39' (digits 0 to 9) of ISO/IEC 8859-1

S: special character, hexadecimal ranges '20' – '2F' (<space> ! “ # $ % & ‘ ( ) * + , - . /), '3A' (:), '3C' – '40' (< = > ? @), '5B' – '60'

([\]^_`),'7B'–'7E'({|}~),'A1'–'AC'(¡¢£¤¥¦§ ©̈   a«¬),'AE'–'A5'(® ̄°±2 3 μ́  ),and'A7'–'BF'(· ̧ 1 ° » 1⁄4 1⁄2 3⁄4 ¿) of ISO/IEC 8859-1

NOTE to entry A, N and S: In this definition ISO/IEC 8859-1 is used for identification of the character and not for encoding. full-date and date-time: according to RFC3339. For date-time, further refined in 3.3 of RFC4287

From: Openid-specs-ekyc-ida <openid-specs-ekyc-ida-bounces at lists.openid.net> On Behalf Of Wesley Dunnington via Openid-specs-ekyc-ida
Sent: Wednesday, February 19, 2020 8:25 AM
To: OpenID eKYC Identity Assurance Working Group <openid-specs-ekyc-ida at lists.openid.net>
Cc: Wesley Dunnington <wesleydunnington at pingidentity.com>
Subject: [EXTERNAL] Re: [OpenID-Specs-eKYC-IDA] place_of_birth vs. birthplace

Irrespective of the final decision on the place_of_birth vs birthplace claim, the schema will change at some point. I would advocate that we add a version identifier to the schema for the 09 version of the spec so we can be prepared for the future.

Wes

On Wed, Feb 19, 2020 at 11:20 AM Torsten Lodderstedt via Openid-specs-ekyc-ida <openid-specs-ekyc-ida at lists.openid.net<mailto:openid-specs-ekyc-ida at lists.openid.net>> wrote:
Hi all,

we haven an open ticket (https://bitbucket.org/openid/ekyc-ida/issues/1119/place_of_birth-birthplace<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbitbucket.org%2Fopenid%2Fekyc-ida%2Fissues%2F1119%2Fplace_of_birth-birthplace&data=02%7C01%7Ctonynad%40microsoft.com%7C434dc26c5de245f6923208d7b55be5c9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637177279271839954&sdata=8RcMTOKUoF%2F7%2ByYdQilKS1F%2FVIfwGbXj%2FAt4ucU%2Fj34%3D&reserved=0>) and an open PR (https://bitbucket.org/openid/ekyc-ida/pull-requests/3<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbitbucket.org%2Fopenid%2Fekyc-ida%2Fpull-requests%2F3&data=02%7C01%7Ctonynad%40microsoft.com%7C434dc26c5de245f6923208d7b55be5c9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637177279271839954&sdata=fansL3kKQ%2BoVNk%2BvT3GmFw9jsQmlmdmp4YOJcOGLMzc%3D&reserved=0>) to change the name of the claim place_of_birth to birthplace.

From the discussions in the recent WG calls I perceive a tendency to not do this change for the following reasons:

- it’s a breaking change. Given there are real implementations of OIDC4IDA out in the wild, this will require really compelling reasons and a concept for version management (which we do not have now).
- A comparison with the terminology used by ICAO 93.3 (part 3) - basis for representation of data at/in official travel documents - revealed that ICAO uses place of birth.

I would like to get your opinion on how to proceed.

What do you think? Shall we (1) close the ticket and PR OR shall we (2) perform the change.

thanks in advance,
Torsten.

--
Openid-specs-ekyc-ida mailing list
Openid-specs-ekyc-ida at lists.openid.net<mailto:Openid-specs-ekyc-ida at lists.openid.net>
http://lists.openid.net/mailman/listinfo/openid-specs-ekyc-ida<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.openid.net%2Fmailman%2Flistinfo%2Fopenid-specs-ekyc-ida&data=02%7C01%7Ctonynad%40microsoft.com%7C434dc26c5de245f6923208d7b55be5c9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637177279271849959&sdata=0dseTcWOqCsqf4h2vy%2Fq9RSFLklxj%2F1HBBNICe89TRE%3D&reserved=0>

--
[Ping Identity]<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pingidentity.com%2F&data=02%7C01%7Ctonynad%40microsoft.com%7C434dc26c5de245f6923208d7b55be5c9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637177279271859948&sdata=UjJyr0pGQ%2BhNxA%2FXSAZ6ZLol8dgBlLL0aPyXKW5pyE0%3D&reserved=0>
Wesley Dunnington
Field CTO East Region
wesleydunnington at pingidentity.com<mailto:wesleydunnington at pingidentity.com>

c: 508-254-5475
Connect with us:
[Glassdoor logo]<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.glassdoor.com%2FOverview%2FWorking-at-Ping-Identity-EI_IE380907.11%2C24.htm&data=02%7C01%7Ctonynad%40microsoft.com%7C434dc26c5de245f6923208d7b55be5c9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637177279271869947&sdata=14l8r6DlmKKkHg4QFgttWOXJZX%2Bc%2FtsqtZ49Hm925XU%3D&reserved=0>[LinkedIn logo]<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2F21870&data=02%7C01%7Ctonynad%40microsoft.com%7C434dc26c5de245f6923208d7b55be5c9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637177279271879939&sdata=Fs3Nw62F09AILnkyvsCbnI6mWWgpO2d4VeqyEtQsdh0%3D&reserved=0>[twitter logo]<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Fpingidentity&data=02%7C01%7Ctonynad%40microsoft.com%7C434dc26c5de245f6923208d7b55be5c9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637177279271879939&sdata=P5whYm%2BvxgP9S76HWs5v3V77doHhv%2BXklA%2FzwQsI5h8%3D&reserved=0>[facebook logo]<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2Fpingidentitypage&data=02%7C01%7Ctonynad%40microsoft.com%7C434dc26c5de245f6923208d7b55be5c9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637177279271889937&sdata=Onc65WCQE7tg4FzZHUeIXjl25CcVVFOPNcb3p4136zQ%3D&reserved=0>[youtube logo]<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtube.com%2Fuser%2FPingIdentityTV&data=02%7C01%7Ctonynad%40microsoft.com%7C434dc26c5de245f6923208d7b55be5c9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637177279271889937&sdata=VVpX052VgFS4LGp6ktKBCtYOq5dlOSzfAyJRxJRLBOs%3D&reserved=0>[Blog logo]<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pingidentity.com%2Fen%2Fblog.html&data=02%7C01%7Ctonynad%40microsoft.com%7C434dc26c5de245f6923208d7b55be5c9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637177279271899932&sdata=E%2BsVHFXQRJfTU9d8kgG6kCwu5sspTs5fakXD13VR8rQ%3D&reserved=0>
[https://www.pingidentity.com/content/dam/ping-6-2-assets/images/misc/emailSignature/2020/rsa-emailsignature.png]<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.pingidentity.com%2Fen%2Fevents%2Fe%2Frsa.html&data=02%7C01%7Ctonynad%40microsoft.com%7C434dc26c5de245f6923208d7b55be5c9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637177279271929918&sdata=fVO%2FGePOBBwzZ%2F1%2F29PEotRNfsb2cknSQkgaWVcwu1I%3D&reserved=0>

CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited.  If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ekyc-ida/attachments/20200219/2ed2a1a4/attachment-0001.html>