Tim Cappalli
Tim Cappalli
Correct. That wasn't in scope for the proposal (#2034)
2024-04-19 WebAuthn F2F meeting: consensus to put this PR (and its alternative #2021) on hold until some details around attestation and conformance in FIDO are ironed out.
+1. This has been driving me crazy.
We're still discussing the potential impact of this (ex: two apps registering openid:// and/or platforms allowing it to be registered).
@awoie we're concerned with multiple parties using openid:// on the same device. While the mail situation is similar, it is still a fairly specific type/action whereas openid:// could be any...
Linked OIDF work item: https://bitbucket.org/openid/connect/issues/1112/register-openid-to-the-well-known-uri
> @timcappalli SIOP mandates `openid://`. anything else such as `wallet://` would not result in SIOP backwards compatibility. is `openid://` overloaded and being used by anything other than SIOP? So there's...
(@simoneonofri @emlun @nadalin fyi)
"origin" should have a normative references to the [HTML spec](https://html.spec.whatwg.org/). I'm not familiar with the template engine being used, so I'm not sure how to add it. Here is what...
Discussed at the 2024-06-21 hybrid meeting ([raw notes](https://github.com/WICG/digital-credentials/wiki/2024-06-21-Hybrid-Meeting-Notes#request-types-credential-types-registries-etc)). > AI Generated Summary (Google Gemini) > > This discussion is about how to handle different types of credential requests and how...