From c01e69a580c4d3dfec3341b21c669d46f4bc16d1 Mon Sep 17 00:00:00 2001 From: Wendy Seltzer Date: Mon, 19 Jul 2021 09:12:07 -0400 Subject: [PATCH] [webauthn] Update coordination to match template As requested by i18n https://github.com/w3c/strategy/issues/263#issuecomment-880215489 --- 2021/webauthn-2021.html | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/2021/webauthn-2021.html b/2021/webauthn-2021.html index 58ea5e20..d289ee7e 100644 --- a/2021/webauthn-2021.html +++ b/2021/webauthn-2021.html @@ -270,8 +270,16 @@

Success Criteria

Coordination

-

For all specifications, this Working Group will seek horizontal review for accessibility, internationalization, performance, privacy, and security with the relevant Working or Interest Groups, and with the TAG. Invitation for review will be issued during each major standards-track document transition, including FPWD and CR, and should be issued when major changes occur in a specification.

- +

For all specifications, this Working Group will seek horizontal review for + accessibility, internationalization, performance, privacy, and security with the relevant Working and + Interest Groups, and with the TAG. + Invitation for review must be issued during each major standards-track document transition, including + FPWD. The + (Working|Interest) Group is encouraged to engage collaboratively with the horizontal review groups throughout development of + each specification. The (Working|Interest) Group is advised to seek a review at least 3 months before first entering + CR and is encouraged + to proactively notify the horizontal review groups when major changes occur in a specification following a review.

+

This API should work with a wide variety of authenticators and should not require non-standardized vendor-specific infrastructure. We will establish liaisons with the other standards bodies working on particular authenticators as needed.