Re: [w3ctag/design-reviews] Web Translation API (Issue #948)

Hi Domenic - Our feedback that we sent above stands, particularly regarding the name space of this API. We don't think it belongs in a `.ai` namespace. We think that the name spaces should be funciton-led rather than technology-used-to-deliver-the-function-led. Your proposal under [point 6](https://github.com/w3ctag/design-reviews/issues/948#issuecomment-2257382202) (`AITranslatorCapabilities`) is a step forward but we would prefer `Translator.capabilities()`. We also think your response to point 3 of our feedback is fine. We also would strongly encourage that the spec include a non-normative note encouraging the use of professional translation services where possible (point 7 of our original feedback). Please consider this. We're going to close as `satisfied with concerns` due to these concerns. Given the current state of the spec, and lack of venue, we understand this to be an early review. We expect that addressing the points above will be important for further standardization. ✨

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/948#issuecomment-2274380634
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/948/2274380634@github.com>