-
Notifications
You must be signed in to change notification settings - Fork 21
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
Alignments of Data Model Section with SD-JWT and SD-JWT-VC latest drafts #511
base: versione-corrente
Are you sure you want to change the base?
Conversation
…side credential metadata type
Removed also unique_id attribute. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tax_id_code
and unique_id
are still present in non normative examples of the following sections:
- Entity Configuration of PID/(Q)EAA Providers
- Entity Configuration of Relying Parties
- PID/(Q)EAA Data Model (in the mdoc example)
- Relying Party Solution
Removed unique_id and tax_id_code from the non-normative examples reported by @giadas. |
"assurance_level": "high", | ||
"evidence": { | ||
"method": "cie" | ||
"verification": [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this non-normative example the assurance_level
and evidence
sub-values are missing.
* ``evidence``: It MUST contain ``method`` claim identifying the digital identity system used for the authentication. | ||
- [SD]. Object containing user authentication and user data verification information. It is REQUIRED only if the Credential type is PersonIdentificationData, and it MUST not be included in other Credential types. It MUST include the following sub-value: | ||
|
||
* ``assurance_level``: String identifying the level of identity assurance guaranteed during the User authentication process. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not clear, considering the PersonIdentificationData, are there cases where the identity assurance level during the User authentication process is not high?
This PR:
List changes introduced: