- From: Jeffrey Yasskin <notifications@github.com>
- Date: Tue, 11 Feb 2025 15:18:38 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 11 February 2025 23:18:42 UTC
We discussed this in a breakout today: We think it's a useful advance to help websites recognize a user's speech on their local device, in line with our [data minimization guidance](https://www.w3.org/TR/privacy-principles/#data-minimization). We see in the I2S thread that [the CG is actively iterating on the shape of this API](https://groups.google.com/a/chromium.org/g/blink-dev/c/VNOok2dbmHM/m/cz7ZnL59AAAJ), and we'd like to let them come to some conclusions before we review the result. We've opened a [design principles issue](https://github.com/w3ctag/design-principles/issues/551) on the architectural issues around downloading large data files to support browser APIs, which apply across this and the [Translation](https://github.com/webmachinelearning/translation-api) and [Writing Assistance](https://github.com/webmachinelearning/writing-assistance-apis) APIs. We'll close this review for now, but please comment when the WG is closer to consensus or has architectural questions about the API. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1038#issuecomment-2652277946 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1038/2652277946@github.com>
Received on Tuesday, 11 February 2025 23:18:42 UTC