search

eu-digital-identity-wallet / eudi-doc-architecture-and-reference-framework

The European Digital Identity Wallet
https://eu-digital-identity-wallet.github.io/eudi-doc-architecture-and-reference-framework/
Other
431 stars 60 forks source link

DC4EU Feedback: Clarifications on the naming attributes in PIDs and equivalence of values between ISO/IEC 18013-5 and SD-JWT formats #220

Open DC4EU-Consortium opened 4 months ago

DC4EU-Consortium commented 4 months ago

Providing clear transcription rules for the given and family name fields—such as guidelines on capitalization, character encoding, multivalue semantics, and language use—would significantly enhance the consistency and harmonization of these mandatory fields across Member States.

Establishing common standards for these attributes in both formats would reduce errors, improve data interoperability, and facilitate the seamless provisioning of personal accounts to online services across borders. Furthermore, we consider the reintroduction of naming attributes that incorporate the language of the issuing country to be crucial. This approach aligns with best practices adopted by other standardization bodies working with personal data on international scenarios.

digeorgi commented 1 week ago

Thank you for your feedback.

We are not totally sure we understand your remark. Are you referring to the identifiers for attributes used in ISO-compliant PIDs versus those in SD-JWT VC-compliant PIDs? If so, please see comment #160 .

If, on the other hand, you are referring to the value of these attributes, we do not see any need for change. You mention:

capitalization -> The ARF is not in a position to force Member States to adopt a specific convention on the capitalization of names. National conventions differ throughout the Union, and we don't see a need for harmonization. character encoding -> As you know, we have chosen to use UTF-8 encoding and to support the full Unicode character set. (See also issue #157
We don't see a need for any further specification of character encodings. Please let us know in case you have specific requirements in mind.

multivalue semantics -> We are not sure what you mean by this. Please clarify and reference the specific PID attribute(s) for which you see a challenge.

language use -> We believe that for the attributes currently specified in the PID Rulebook, it is not necessary to indicate the language used. Please let us know of any specific challenges you see. Regarding a reintroduction of naming attributes that incorporate the language of the issuing country: As said above, tstr attributes support the full Unicode character set. Issuing countries can therefore use their national characters for names. It is up to the Relying Party to transcribe this to Latin1 or any other characters, if they so choose.