Tim Cappalli
Tim Cappalli
From #43: > support for selective disclosure could be mandated to be included in the registry for "protocol"
Cleaning up old issues. This was addressed in OID4VP.
@npdoty it's the wallet that ultimately needs to present usage information and ask for consent before releasing a presentation. While the information itself may not be passed directly in the...
@npdoty Understood. Do you have a proposal or ideas on how to address this? I can allocate some time on the next meeting's agenda.
@OR13 it is largely out of scope for this specific effort as an extension or PWA would need a separate API for registering with the browser. We have a similar...
Yes, I believe on one of the calls there was loose consensus that this would be out of scope for v1 as it would align closer to the credential provider...
Cleaning up issues. This is an old discussion. The group landed on `navigator.credentials.get|create` with the `digital` type.
2023-11-06 call: * getIdentityAttributes * getClaims * getIdentityClaims * getAttributes * getClaims * requestVerifiableClaim * requestVerifiableAttributes More preferred: * requestClaims * requestAttributes Plan to close in two weeks.
Notes from 2023-11-15 calls: https://github.com/WICG/identity-credential/wiki/2023-11-15-Meeting-Notes#api-design-should-emphasize-that-sites-should-request-minimal-properties-not-full-identity-documents Highlighting an something from the discussion: support for selective disclosure could be mandated to be included in the registry for "protocol".
From 2024-07-29 call, comment added to #58. Closing issue.