Sam Goto

> What this API returns is not a claim it is more the document proving the claim. A credential?

> Could a structure like below be sufficient? Yeah, I do think a variation of this structure would be possible. Here is how we could accomplish this in more WebIDL-friendly...

That’s a great question, and one that deserves some active exploration. I think it is very important to acknowledge that is still an open question. There are many ways to...

`VerifiableCredential` isn't a web-exposed name though, is it?

Thanks for the feedback! Quick clarifying questions! > strong identification/authentication of who's requesting the credential Is requiring HTTPS for the requesting site sufficient for strongly identifying the requestor? > clear...

> An origin, with transport guaranteed by HTTPS, is a good starting point, if it's limited to the top-level page. Yeah, good point: I think we can easily limit the...

> The charter should consider the design approach taken in the Credential Handler API (CHAPI) and the Verifiable Presentation Request (VPR) work. Namely, that the design is meant to be...

A sub question here is: * Should Query Languages be format specific (e.g. one for VCs and one for mDocs and one for whatever comes next) or format-agnostic?

@npdoty: I'd like to understand what kinds of abuse mitigations we'd like to have and how would that impact the query languages ... https://github.com/WICG/identity-credential/issues/30 @npdoty: when you say: > clear...

Ah yeah, good point. Since you kicked this off, we [introduced](https://github.com/WICG/identity-credential/blob/main/identity-credential-proposal.md) a `params` object, which is a grab-bag of key-value pairs that is sent to wallets (and OIDC providers) after...