[blink-dev] Intent to Continue Experimenting: Handwriting Recognition API
Jiewei Qian
Contact emails
q...@chromium.org, hong...@chromium.org, mgi...@chromium.orgExplainer
https://github.com/WICG/handwriting-recognition/blob/main/explainer.mdSpecification
Summary
An API for web applications to make use of advanced handwriting recognition services (e.g. those on operating systems) to recognize text from handwriting drawings (inks) in real time. In this context, handwriting drawing means the temporal and positional information used to describe a human handwriting process.
Blink component
Blink>HandwritingTAG review
https://github.com/w3ctag/design-reviews/issues/591TAG review status
PendingRisks
Interoperability and Compatibility
Different browsers (and operating systems) will expose different underlying implementations and produce different outputs given the same input. We think this is acceptable given the implementation is machine-learning based, and it is not feasible or desirable to precisely specify the expected output for a given input in a standard. In the past, we have taken this approach for the Web Speech and Shape Detection APIs.
Gecko: No signal (https://github.com/mozilla/standards-positions/issues/507) Feedback requested, no reply yet.
WebKit: No signal (https://lists.webkit.org/pipermail/webkit-dev/2021-March/031762.html) Feedback requested, no reply yet.
Web developers: No signals Filed https://github.com/WICG/handwriting-recognition/issues/21
Goals for experimentation
- General API design. Determine if the API design satisfies the App developer's use cases - Specifically, we want to see if the current API design provides sufficient information (in the result) to enable web developers to make use of this feature.
Reason this experiment is being extended
We want to propose a new API design for querying language supports, which is easier to understand, and more extensible in the future. This change is targeting M95. Proposal: https://github.com/WICG/handwriting-recognition/pull/20 This will be a minor breaking change, web developers have to update their feature detection code to keep using the feature. We want to extend the origin trial to avoid disruption to existing clients. This can alternatively be set up as a V2 origin trial. Revised timeline: Original origin trial - first milestone: M91 Original origin trial - last milestone: M94 Proposed change implementation: M95 Extended origin trial - last milestone: M97
Ongoing technical constraints
None
Debuggability
N/A. Existing DevTools tooling works for this feature.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
NoInitially we will implement this feature on Chrome OS, since it has handwriting recognition service ready for use. We will need to do additional work to integrate with other platforms. Handwriting recognition capabilities already exist on all other platforms. We will do other I2E / I2S for implementing this on other platforms, due to the different security and privacy implications.
Is this feature fully tested by web-platform-tests?
NoFlag name
Requires code in //chrome?
FalseTracking bug
https://crbug.com/1207667Launch bug
https://crbug.com/1206121Estimated milestones
| OriginTrial desktop first | 91 |
| OriginTrial desktop last | 97 |
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5263213807534080Links to previous Intent discussions
Intent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/VXUq1UY4m7YIntent to Experiment: https://groups.google.com/a/chromium.org/g/blink-dev/c/o8RqlFwZItQ/m/vgHLF_pHBQAJ
Thomas Steiner
Contact emails
q...@chromium.org, hong...@chromium.org, mgi...@chromium.orgExplainer
https://github.com/WICG/handwriting-recognition/blob/main/explainer.mdSpecification
Summary
An API for web applications to make use of advanced handwriting recognition services (e.g. those on operating systems) to recognize text from handwriting drawings (inks) in real time. In this context, handwriting drawing means the temporal and positional information used to describe a human handwriting process.
Blink component
Blink>HandwritingTAG review
https://github.com/w3ctag/design-reviews/issues/591TAG review status
PendingRisks
Interoperability and Compatibility
Different browsers (and operating systems) will expose different underlying implementations and produce different outputs given the same input. We think this is acceptable given the implementation is machine-learning based, and it is not feasible or desirable to precisely specify the expected output for a given input in a standard. In the past, we have taken this approach for the Web Speech and Shape Detection APIs.
Gecko: No signal (https://github.com/mozilla/standards-positions/issues/507) Feedback requested, no reply yet.
WebKit: No signal (https://lists.webkit.org/pipermail/webkit-dev/2021-March/031762.html) Feedback requested, no reply yet.
Web developers: No signals Filed https://github.com/WICG/handwriting-recognition/issues/21
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANFkJJkwiFwAFVq5t7UN_YQG%2BEAcSRQH-JMhTfSLkgpnjjLeUQ%40mail.gmail.com.
Google Germany GmbH, ABC-Str. 19, 20354 Hamburg, Germany
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
Registergericht und -nummer: Hamburg, HRB 86891
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.1.23 (GNU/Linux)
iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom.hTtPs://xKcd.cOm/1181/
-----END PGP SIGNATURE-----
Yoav Weiss
On Mon, Aug 23, 2021 at 5:45 AM Jiewei Qian <q...@chromium.org> wrote:
Explainer
https://github.com/WICG/handwriting-recognition/blob/main/explainer.mdSpecification
Summary
An API for web applications to make use of advanced handwriting recognition services (e.g. those on operating systems) to recognize text from handwriting drawings (inks) in real time. In this context, handwriting drawing means the temporal and positional information used to describe a human handwriting process.
Blink component
Blink>HandwritingTAG review
https://github.com/w3ctag/design-reviews/issues/591TAG review status
PendingRisks
Interoperability and Compatibility
Different browsers (and operating systems) will expose different underlying implementations and produce different outputs given the same input. We think this is acceptable given the implementation is machine-learning based, and it is not feasible or desirable to precisely specify the expected output for a given input in a standard. In the past, we have taken this approach for the Web Speech and Shape Detection APIs.
Gecko: No signal (https://github.com/mozilla/standards-positions/issues/507) Feedback requested, no reply yet.
WebKit: No signal (https://lists.webkit.org/pipermail/webkit-dev/2021-March/031762.html) Feedback requested, no reply yet.
Web developers: No signals Filed https://github.com/WICG/handwriting-recognition/issues/21
I would say it's fair to say the developer signal is positive:- There is positive chatter about the API on Twitter (https://twitter.com/search?q=%22handwriting%20recognition%20api%22&src=typed_query&f=live which counts according to https://docs.google.com/document/u/2/d/e/2PACX-1vRikx3FbTlbAj_vkyIx4QITkMO-rnB7AV0kjzjRPPKTIBr-Ll1i3Ue5CJ5eHir-0ifmHwB8gRYisKbg/pub#:~:text=online%20social%20networking).- There are also a number of client-side implementations of the handwriting recognition feature that could profit from an integration with the API (https://github.com/topics/handwriting-recognition?l=javascript which counts according to https://docs.google.com/document/u/2/d/e/2PACX-1vRikx3FbTlbAj_vkyIx4QITkMO-rnB7AV0kjzjRPPKTIBr-Ll1i3Ue5CJ5eHir-0ifmHwB8gRYisKbg/pub#:~:text=client-side%20implementations%20of%20libraries%20that%20(in%20part%2C%20if%20not%20fully%20doable%20on%20the%20client-side)%20do%20what%20the%20feature%20proposes).
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANFkJJkwiFwAFVq5t7UN_YQG%2BEAcSRQH-JMhTfSLkgpnjjLeUQ%40mail.gmail.com.
Jiewei Qian
On Monday, August 23, 2021 at 8:43:49 AM UTC+2 Thomas Steiner wrote:
On Mon, Aug 23, 2021 at 5:45 AM Jiewei Qian <q...@chromium.org> wrote:
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANFkJJkwiFwAFVq5t7UN_YQG%2BEAcSRQH-JMhTfSLkgpnjjLeUQ%40mail.gmail.com.
--
Google Germany GmbH, ABC-Str. 19, 20354 Hamburg, Germany
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
Registergericht und -nummer: Hamburg, HRB 86891
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.1.23 (GNU/Linux)
iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom.hTtPs://xKcd.cOm/1181/
-----END PGP SIGNATURE-----
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/9041d857-3c35-4fba-8933-ab54580aca9an%40chromium.org.
Yoav Weiss
I'll update Web developer signal to positive.We have developers using OT, their feedback is: "Moderately easy" to use and "Extremely likely" to keep using. I haven't seen comments on changing the API design to better support their use cases.
On Thu, Aug 26, 2021 at 12:26 AM Yoav Weiss <yoav...@chromium.org> wrote:On Monday, August 23, 2021 at 8:43:49 AM UTC+2 Thomas Steiner wrote:On Mon, Aug 23, 2021 at 5:45 AM Jiewei Qian <q...@chromium.org> wrote:Contact emails
q...@chromium.org, hong...@chromium.org, mgi...@chromium.orgExplainer
https://github.com/WICG/handwriting-recognition/blob/main/explainer.mdSpecification