Related to this, there is also the matter of Credential Offers--VC-like objects that aren't fully populated or signed, but could be populated with a wallet and signed by an issuer upon verification of the information. For example, an issuer wants to know which one of your multiple valid DIDs/URIs they should use as the credential subject. On Fri, Dec 18, 2020, at 7:16 PM, Liam McCarty wrote: > Fully support this! We’ve been using our own version of verifiable requests from the beginning because there’s really no choice for many use cases. (Or rather, there’s no choice but to have some notion of requests — and may as well make them verifiable.) > > Liam > > *Liam McCarty* > Co-Founder of Unum ID <http://www.unumid.org/> > >> On Dec 18, 2020, at 6:08 PM, Gabe Cohen <gabe.cohen@workday.com> wrote: >> >> Hi CCG folks, >> >> We at Workday are working on wrapping Presentation Exchange <https://identity.foundation/presentation-exchange/> requests and notice there is a gap in the VC-Data-Model. There is a section on Verifiable Presentations <https://w3c.github.io/vc-data-model/#presentations>, but not Verifiable Requests. >> What about adding pretty much the same language as VPs, but for VRs — wrapping a request for credentials with some metadata and a proof? >> >> Happy to collaborate on getting this added. >> >> Gabe
Received on Saturday, 19 December 2020 00:23:46 UTC