- changed status to open
specify how ekyc-ida syntax can be used with Verifiable Credentials
Being able to express how the Issuer verified user claims when issuing a verifiable credential would be an important enhancement.
This might be out of scope for OIDC4VCI specification but it would be good to clarify where this work should happen. and this might also be relevant for OIDC4VP.
Comments (6)
-
reporter -
reporter it was suggested that evidence property can be used: https://www.w3.org/TR/vc-data-model/#evidence
sounds like we need to define a type, but otherwise, can include ekyc-ida syntax in an evidence property
-
One could also consider to include the
verification
element as defined in the eKYC spec (https://openid.net/specs/openid-connect-4-identity-assurance-1_0.html#name-verification-element) into the VC Data Model. It has comprehensive support for trust frameworks, identity assurance levels, evidence, verification&validation methods, process information (transaction ids, agents involved), and even attachments of document scans. -
The next step seems to be to create a concrete proposal.
-
reporter Discussed with Mark Haine and Giuseppe. The gap in VC is the lack of a way to express claims metadata. there might be two options;
- use `verification` container defined in Section 5.1 of ekyc-ida
- Split out JSON schema for `verification` container, and refer to it in another schema
-
reporter - changed status to closed
there is a work happening in this issue in vc-data-model GitHub repository and here is a document with a concrete proposal: https://docs.google.com/document/d/1htujrb-_1kh8tkV4MXYRmZ44m_D7yFrY09aFJkAz7io/edit Closing issue since I think the work should continue there.
- Log in to comment
2022-01-27 draft and discuss in vc-data-model-v2