- From: cynthia <notifications@github.com>
- Date: Wed, 26 Jul 2017 16:41:05 +0000 (UTC)
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/176/318111564@github.com>
> That's correct, Mac provides only the bounding boxes but not the result of any OCR inside of them. (Whereas Android and Win10 do seem to support OCR, see links in the Example of the Spec). > > I guess in this case developers should rely on polyfills, probably using Tesseract -- but you had some concerns about its performance beyond pure document scanning use cases, right? That is correct. It seems more likely that the raster image that one would acquire from a web application would be more likely to be something from a camera rather than a flatbed scanner, which will most likely have perspective distortion. I am not against the API, but I would like to tread carefully - especially in a high level, feature specific API like this. > Are you proposing treating Face+Barcode and Text differently? Yes. To move the spec forward sooner - I would actually want to propose moving text out to a separate spec or a next major revision of the standard, both to reduce implementor workload for conformance and to ship a better standard. > Aside from this last remark, I understand from this discussion that the Spec looks good TAG-wise ? (Notwithstanding specific Issues to be filled). Yes, indeed. Thanks for bringing this to our attention! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/176#issuecomment-318111564
Received on Wednesday, 26 July 2017 16:41:53 UTC