An idea on the way forward for Verifiable Claims

All,

Sorry I missed the call yesterday as I was travelling. I looked at the
minutes and wanted to share an idea I had.

I believe that what the VCTF needs to do next is prove that there is a need
for VC and they could do this in the payments domain (in conjunction with
the WPWG) in the following way:

1. Author a basic VC specification that describes how to sign and verify
data that could be part of the custom payment method data in a payment
request/response.
2. Assist the WG to author a number of the Payment Transaction Messaging
specifications that are required to cover the many flows that are in scope
for that group.
3. Where appropriate, make the VC spec a dependency of these and embed VC
in these messages.

The result is that you potentially have a large number of financial
institutions as early adopters and contributors to this work as they
grapple with building payment apps to support the many payment methods we
have defined in our flows.

This would help to validate that the work is solving the problem it
attempts to solve and also build a core group of implementers.

This "incubation" of the work should be enough to justify formation of a WG
to take the VC spec through the standards track, especially if you have
some non-payments users that are implementing the same spec.

Adrian