- From: Philippe Le Hegaret via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Apr 2024 02:49:04 +0000
- To: public-privacy@w3.org
plehegar has just labeled an issue for https://github.com/w3c/strategy as "Horizontal review requested": == [wg/fedid] Adding Digital Credentials to the FedID WG == # Evaluation A core part of our *Strategic* work is the evaluation of how proposed work serves the Web. In the "Evaluation" phase at the end of the funnel, we make the case whether work is ready to proceed to Chartering of a Recommendation-track deliverable. At that point, we need to identify: * Will this work help to lead the web to its full potential? This work will enable user agents to mediate access to, and presentation of, digital credentials such as a driver's license, government-issued identification card, and/or other types of digital credential. * Is the work Rec-track ready? Not yet, but there is a [proposal in WICG](https://wicg.github.io/digital-identities/). It has been proposed to add this uto the [FedID WG charter](https://github.com/w3c/strategy/issues/427#issuecomment-1973246676). * Do we have the ecosystem of participants needed to make the work successful? Seems so., The relationship with our work on Verifiable Credentials, the work on mDoc, and other systems needs to be refined. digging deeper: Will it add value? * something good for web users. what are the alternatives? * have "horizontal" (a11y, i18n, security, privacy) issues been considered and identified? * what's its importance/opportunity cost? Will we be able to make it succeed? * right participants interested. What does the ecosystem look like? * implementation likely * manageably sized problem * achievable timeline * minimum viable product * does it raise architectural issues that need to be addressed before it can succeed? Special considerations? * risk factors: see [comment](https://github.com/w3c/strategy/issues/427#issuecomment-1973991454) * incentives * openness, decentralization ## Procedural - [AC meeting session on "Identity on the Web"](https://www.w3.org/2024/04/AC/ac-agenda.html#tuesday) on April 9, 2024 - In parallel, https://github.com/w3c/charter-drafts/pull/484 needs to be refined, so that a draft charter can be produced - Goal is to send an advance notice on this right after, assuming no red flag comes up. - Horizontal review of charter to happen between mid-april and mid-may. (already trying to do this in parallel so that we can reduce this). - AC review of the charter mid-may to mid-June (or earlier if horizontal review is closed sooner) - new charter approved in mid-June, unless we get substantial comments. cc @hlflanagan @wseltzer @asr-enid @timcappalli @marcoscaceres @samuelgoto @simoneonofri See https://github.com/w3c/strategy/issues/450 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 18 April 2024 02:49:05 UTC