-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Harmonizing Identity-Related Web Platform APIs #49
Comments
Thank you for proposing a session! You may update the session description as needed and at any time before the meeting, but please keep in mind that tooling relies on issue formatting: follow the instructions and leave all headings and other formatting intact in particular. Bots and W3C meeting organizers may also update the description, to fix formatting issues or add links and other relevant information. Please do not revert these changes. Feel free to use comments to raise questions. Do not expect formal approval; W3C meeting organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting. |
@timcappalli, is this session intended as follow up to the session we are discussing for Monday afternoon? |
No, I'd like to keep payments out of scope for this one as it's being discussed in other sessions. |
Would you mind updating the description to clarify that the scope is not intended to include payments, and we intend to hold more payments-focused discussion on Monday afternoon within the Web Payments WG meeting? |
Sure. I highlighted the topics to be discussed in the description, but I can add an explicit mention of payments. |
Session description
There are currently three active work streams for identity-related Web Platform APIs in the W3C: the Digital Credentials API (DC API), Federated Credential Management (FedCM), and the Web Authentication API (WebAuthn).
In each of these work streams, there have been some common discussion items including flexible but privacy preserving error codes, selector experience and query syntax, conditionally mediated flows, credential and user account identifiers, along with discussion around how these APIs should interact in the future (ex: requesting a VDC -or- an OIDC ID Token in one call). NOTE: Payments will be out of scope for this discussion.
This breakout is intended to be a collaborative, working session. The focus will be on gaining consensus on the more tactical items like errors codes and selectors, with some time at the end reserved for forward looking ideas.
Session goal
This breakout is intended to be a collaborative, working session. The focus will be on gaining consensus on the more tactical items like errors codes and selectors, with some time at the end reserved for forward looking ideas.
Additional session chairs (Optional)
@samuelgoto, @marcoscaceres, @MasterKale
Who can attend
Anyone may attend (Default)
IRC channel (Optional)
#identity-harmony
Other sessions where we should avoid scheduling conflicts (Optional)
#10, #12, #16, #24
Instructions for meeting planners (Optional)
No response
Agenda for the meeting.
https://docs.google.com/document/d/15IiQS0yPzWML3zRHGQ_JQ5xAO5bIgrcJE3sNdwrgSHk/
Links to calendar
The text was updated successfully, but these errors were encountered: