You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PID in SD-JWT (VC) format should follow IANA naming conventions and other JWT best practices. There should be clear description how to map PID CDDL attribute names into IANA claims (For example, nationality ..> nationalities, birth_date → birthdate etc.).
Substantial additional effort would be needed urgently in defining and describing the SD-JWT (VC) details of the PID. Remote online usage is the MOST important use case of the EUDI wallet.
The text was updated successfully, but these errors were encountered:
A pull request was done already to propose an SD JWT VC-compliant PID encoding. See our reply to that PR #160.
In addition, to avoid conflicting claim names, we will add the following requirement to Topic 12: For [SD-JWT VC]-compliant attestations, all claim names SHALL either be included in the IANA registry for JWT claims or be a Public Name as defined in RFC 7519.
PID in SD-JWT (VC) format should follow IANA naming conventions and other JWT best practices. There should be clear description how to map PID CDDL attribute names into IANA claims (For example, nationality ..> nationalities, birth_date → birthdate etc.).
Substantial additional effort would be needed urgently in defining and describing the SD-JWT (VC) details of the PID. Remote online usage is the MOST important use case of the EUDI wallet.
The text was updated successfully, but these errors were encountered: