digital-credentials

digital-credentials copied to clipboard

DigitalCredentialRequestOptions.requests should probably be a required member, even if it's empty. Checking if it's empty is done in "7.4 [[DiscoverFromExternalSource]](origin, options, sameOriginWithAncestors) internal method", step 7.

marcoscaceres

Topic: should the .create call allow multiple request objects, and if so, what constraints should be applied? Consensus from the [2025-03-10 call](https://github.com/WICG/digital-credentials/wiki/2025-03-10-Meeting-Notes#204-httpsgithubcomwicgdigital-credentialspull204-for-issuance) was to allow multiple request objects with the...

timcappalli

multi-wallet requests

2

I am sorry if this is a duplicate - I think there was an issue somewhere, but can't find it right away. Is there a plan to handle a situation...

Sakurann

Checks for data validity happen mostly at the WebIDL binding layer. As such, we should probably move the requests' size check earlier (before we consume user activation).

marcoscaceres

The digital credential definition should include "verifiable" aspect

1

NIST has a nice definition. @timcappalli, what's the link to the blog post?

marcoscaceres