You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proofreading is the process of examining a text carefully to find and correct errors such as grammar, spelling, and punctuation to generate an error-free text before it is published or shared. Browsers and operating systems are increasingly offering proofreading capability to help their users compose (examples: Example, Example). Web applications can also benefit from such proofreading capability backed by language models for a variety of use cases.
We're proposing an API that uses language models to give web developers high-level functionalities for proofreading. Specifically:
Error Correction: Correct input text by the user
Error Labeling: For each correction made to each error in the input text, label the error type (e.g. spelling, punctuation, etc.)
Error Explanation: Annotates each error with a plain language explanation
It's possible this might fit well under the "Writing Assistance APIs" banner, hosted at https://github.com/WICG/writing-assistance-apis/ . Although, it is different from those in some ways, e.g. in having a more structured output. So, I am not sure what structure is best for organizing the specifications.
Introduction
Proofreading is the process of examining a text carefully to find and correct errors such as grammar, spelling, and punctuation to generate an error-free text before it is published or shared. Browsers and operating systems are increasingly offering proofreading capability to help their users compose (examples: Example, Example). Web applications can also benefit from such proofreading capability backed by language models for a variety of use cases.
We're proposing an API that uses language models to give web developers high-level functionalities for proofreading. Specifically:
Read the complete Explainer.
Feedback
We welcome feedback in this thread, but encourage you to file bugs against the Explainer.
The text was updated successfully, but these errors were encountered: