Re: VC-API JFF PlugFest 2 Questions

Hi Kayode - great questions!

For the JFF PlugFest, we've put together tooling that uses CHAPI to
directly communicate a Verifiable Credential.  The
https://playground.chapi.io site uses VCAPI on the backend to connect to
various issuer sites.  This is a simplified workflow that can get
developers up-and-running without the need to implement a credential pickup
using VCAPI /exchanges.

For /exchanges workflows, we recommend using CHAPI to communicate the URL
of the /exchanges endpoint.  The individual navigates to an issuer site
which wants to issue a Credential.  The issuer site initiates a CHAPI
request, which allows the individual to select a wallet to process the
request.  The use of CHAPI here preserves the individual's choice of wallet
and avoids the assumptions you noted would be required in the QR code or
deep-link examples.  The wallet then hits the specified /exchanges endpoint
and receives a Verifiable Presentation containing the Credential.



We’ve added an example to the Verifiable Presentation Request (VPR) spec to
show how an issuer can ask for DID Authentication and then point the wallet
at /exchanges endpoint to perform the Auth-Pickup workflow:
https://w3c-ccg.github.io/vp-request-spec/#example-example-interact-request


In this example, the `interact` field describes the type and URL of the
/exchanges endpoint.  The `type` is an `UnmediatedPresentationService2021`,
which is outlined in the VCAPI spec:
https://w3c-ccg.github.io/vc-api/#exchange-examples

Best Regards,

Evan
--
Evan Lally
Digital Bazaar, Inc.
https://www.digitalbazaar.com/