- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Tue, 19 May 2020 11:21:33 +0200
- To: public-webauthn-adoption@w3.org
Hi, Here are the notes I took during our call yesterday. Next steps: * wireframe project would benefit from aligning with How-To-FIDO paper (pending review from FIDO process, and informal input from the CG) * figure out how to host our wireframe project (Dom to start discussion on the list) * candidate language/frameworks include Ruby on Rails (Bart), Java + Angular (StrongKey) * we need to strengthen participation and input from UX people to the group / project (Cindy will bring her initial input to the challenges document) Next call on June 1st at 5pm UTC - Webex invitation to be sent to the internal mailing list. Present: Dom, Arshad, Cindy, Luke Walker, Suby, Tim Cappalli ----- New participants intros: Cindy: Well Fargo Auth team for virtual channel, leading impl of rolling out Fido WebAUthn to consumers based o nWindows Hello Suby: duo, led impl in auth prompt David Chadwick: Verifiable credentials, impl based on FIDO2 distribution ----------- Adoption challenges / How to Fido Doc Arsahd: we need to avoid creating confusion by multiplying terminology Dom: agree getting extreme clarity on terminology and avoid divergence across FIDO/W3C, but also across implementors, adopters John: +1 - we need to see how to align languages, see where the How To Fido doc from Google stands Arshad: still need to review the doc Nick: great UX work between Shopify & Google; need to continue good cooperation between W3C & FIDO Suby: so far, too little guidance on UX for relying party - good thing if this group could help Andrew: FIDO issues FIDO papers; this How-to-FIDO paper will be brought forward as a new FIDO paper in the FIDO2 WG and get wider reviews from FIDO alliance this group would be good to bring informal feedback this complements the high-level visual cues the paper hits the sweet spot for product owners Dom: re-use beyond FIDO white paper? Andrew: open to use by the public; modification might be more tricky how to engage dev community - W3C uniquely positioned for that Nick: timeline for the paper? Andrew: no clear timeline at this point it needs clearance by the Board of Director (this week), then will be brought to FIDO2 Technical WG, seeking input from other groups, then final editing - anywhere from a couple to several weeks - guess 6 to 8 weeks John: that sounds doable Andrew: need to check what the W3C liaison enables; could enable Dom to contribute ot that Nick: the sooner we get the doc out, the better --------- Shopify Webauthn UX / Wireframe project Bart: How-to-FIDO is more up to date than what we did a year ago in Shopify would be happy to build a wireframe with best UX practices for Rails with to the Howtofido PoC - having a working demo with all the best UX practices other communities to target: PHP, Java, C# Arshad: SK can create a Java (Back-end) + Angular (Front-End) Dom: how would we structure this? Bart: one github org to host one-repo-per-language repos? Arshad: shouldn't FIDO host this? Nick: given this is done in W3C space, should this be done in W3C? Andrew: let's look at the group's deliverables and figure out where they reside Dom: we need to figure what requirements we want to fulfill with the wireframe project Suby: we need input from UX Cindy: I'm coming from the customer perspective John: FIDO has also UX work Nick: we should set time aside on these calls for this UX input John: we have a UX lead who could come up with a list of things to tackle Nick: re communicating together, having the framework out around the same time as the FIDO paper would be good Cindy: variation across browsers in terms of customization of UI; hard-to-grok terminology consumer recognition
Received on Tuesday, 19 May 2020 09:21:36 UTC