Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PID set: Potential issue with uniqueness in mandatory attribute set #159

Closed
jantdm opened this issue Mar 25, 2024 · 3 comments
Closed

PID set: Potential issue with uniqueness in mandatory attribute set #159

jantdm opened this issue Mar 25, 2024 · 3 comments
Labels
user story User story description

Comments

@jantdm
Copy link
Contributor

jantdm commented Mar 25, 2024

Description

In section 5.1.1.1 one of the principles states "No two persons SHALL have the same PID set of values for mandatory attributes." Based on the mandatory set of attributes as specified in 5.1.1.2 the combination of family and given name with birth date will lead to a very small but still non-zero number of cases with persons having the same PID set of values in a population of 450m.

(Using given_names (plural) instead or adding this in the mandatory set could reduce the chances, but not to zero.)
Edit: Just realized that the PID rulebook already specifies given_name as plural "name(s)".

Are these edge cases accepted or is this something where the spec would need to be adapted/extended?

I'm just getting into the process so apologies if this is not relevant here.

@jantdm jantdm added the user story User story description label Mar 25, 2024
@ivanek666
Copy link

There are several cases of tuples Name, Surname and Date of birth just in Czech Republic according to state data https://archi.gov.cz/en:nap:iseo

This principle cannot be achieved.

@jantdm
Copy link
Contributor Author

jantdm commented Mar 25, 2024

There are several cases of tuples Name, Surname and Date of birth just in Czech Republic according to state data https://archi.gov.cz/en:nap:iseo

This principle cannot be achieved.

Very interesting, thank you for posting. I was quickly looking for something like this but mostly found news articles of examples and theoretical statistics. This is a perfect empirical example.

So the issue is much more significant, 25 000 people that could not uniquely be identified for the Czech Republic alone.

@jantdm
Copy link
Contributor Author

jantdm commented Apr 24, 2024

Following up on this, a unique identifier was part of the mandatory data set in the ARF up until the changes introduced with issue #67. Is there a reasoning available for the removal of the respective line?

2015/1501 (https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32015R1501) which was referenced before as a source for the requirement also still references the need for a unique identifier.

@eu-digital-identity-wallet eu-digital-identity-wallet locked and limited conversation to collaborators Apr 29, 2024
@skounis skounis converted this issue into discussion #168 Apr 29, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
user story User story description
Projects
None yet
Development

No branches or pull requests

2 participants