W3C home > Mailing lists > Public > public-credentials@w3.org > July 2021

Re: Bikeshed: Renaming the VC HTTP API

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sat, 17 Jul 2021 12:47:38 -0400
To: W3C Credentials CG <public-credentials@w3.org>
Message-ID: <a09bc5d8-9f1f-fe8b-06c2-f83bfb8c480f@digitalbazaar.com>
On 7/17/21 12:23 PM, Orie Steele wrote:
> Web Credentials, WebVC...

Interestingly, we started (many years ago... 7+) with "Web Credentials"... and
then "Identity Credentials"... and then "Verifiable Claims"... and finally
"Verifiable Credentials":


That evolution took around 4 years. :)

> I'm still struggling to see how this API is anything other than fancy KMS
> interface that only signs and verifies JSON LD VCs... If cross trust domain
> cases are supported, that's a different kind of thing...

The API you added suggests that the API crosses trust domains:


> Maybe we should leave the cross trust domain vc apis to didcomm and focus
> on interop behind that layer... Or we should should explicitly embrace that
> use case and add a word like Exchange... Web Credential Exchange, etc...

I was always under the impression that that's where you were going with the
presentation APIs. It's now sounding like you never had that intent (further

... but then you have also said that we can't do what we can do via CHAPI by
using purely HTTP... so, now I'm confused.

In your opinion, Orie, is presentation exchange over HTTP in scope or out of

I had always thought that you were strongly arguing to put it in scope... and
my expectation is that I'm not alone in that assumption (as that is largely
where Adrian's concerns are coming from).

-- manu

Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
News: Digital Bazaar Announces New Case Studies (2021)
Received on Saturday, 17 July 2021 16:47:56 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:25:18 UTC