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

> >  5. We recommend a translation-specific namespace instead of ai.
>
> This is related to some ongoing work on other AI model-based APIs which are not yet at the stage of being ready for TAG review. We want them all to share a namespace and a set of common API patterns (e.g. sibling create() and capabilities() methods; "no"/"readily"/"after-download" availability signals; destroy() methods; specific AbortSignal integration patterns; etc.)

One wonders if, in the future, this will be as meaningless as an API called `computer` or `software`.  Please reconsider.

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

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