{"action":"created","issue":{"url":"https://api.github.com/repos/kba/hocr-spec/issues/17","repository_url":"https://api.github.com/repos/kba/hocr-spec","labels_url":"https://api.github.com/repos/kba/hocr-spec/issues/17/labels{/name}","comments_url":"https://api.github.com/repos/kba/hocr-spec/issues/17/comments","events_url":"https://api.github.com/repos/kba/hocr-spec/issues/17/events","html_url":"https://github.com/kba/hocr-spec/issues/17","id":176955648,"number":17,"title":"Future of hOCR","user":{"login":"kba","id":273367,"avatar_url":"https://avatars.githubusercontent.com/u/273367?v=3","gravatar_id":"","url":"https://api.github.com/users/kba","html_url":"https://github.com/kba","followers_url":"https://api.github.com/users/kba/followers","following_url":"https://api.github.com/users/kba/following{/other_user}","gists_url":"https://api.github.com/users/kba/gists{/gist_id}","starred_url":"https://api.github.com/users/kba/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kba/subscriptions","organizations_url":"https://api.github.com/users/kba/orgs","repos_url":"https://api.github.com/users/kba/repos","events_url":"https://api.github.com/users/kba/events{/privacy}","received_events_url":"https://api.github.com/users/kba/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":17,"created_at":"2016-09-14T16:29:28Z","updated_at":"2016-10-25T18:22:31Z","closed_at":null,"body":"hOCR is easy to implement because it's based on HTML but it can hardly be called a standard while there are living standards for OCR like ALTO.\r\n\r\nhOCR is used by Open Source engines like tesseract, ocropy, kraken, cuneiform. Is their output spec-conformant and uniform? Would it not be better to enhance them to support ALTO if they do not already?\r\n\r\nI like hOCR's approach for extensibility and microformat-like simplicity but it has not been updated for several years and I think it should not be used for new implementations unless there are very compelling reasons not to use ALTO.\r\n\r\nThat being said, there is software around that produces hOCR and related tools that expect hOCR (or some dialect of it).\r\n\r\nWhat I think needs to be done in any case:\r\n\r\n1. Reduce the specs to the parts that are in actual use\r\n2. Restructure it to make it more coherent and provide more examples\r\n3. Produce a new major version indicating those changes and removals.\r\n\r\nThat new version should either be developed/refined further (e.g. by standardizing `x*` properties/classes) or contain a prominent deprecation notice that recommends another format like ALTO.\r\n\r\nCC @tmbdev @mittagessen @zdenop @amitdo @zuphilip @cneud @stweil"},"comment":{"url":"https://api.github.com/repos/kba/hocr-spec/issues/comments/256123066","html_url":"https://github.com/kba/hocr-spec/issues/17#issuecomment-256123066","issue_url":"https://api.github.com/repos/kba/hocr-spec/issues/17","id":256123066,"user":{"login":"tmbdev","id":333887,"avatar_url":"https://avatars.githubusercontent.com/u/333887?v=3","gravatar_id":"","url":"https://api.github.com/users/tmbdev","html_url":"https://github.com/tmbdev","followers_url":"https://api.github.com/users/tmbdev/followers","following_url":"https://api.github.com/users/tmbdev/following{/other_user}","gists_url":"https://api.github.com/users/tmbdev/gists{/gist_id}","starred_url":"https://api.github.com/users/tmbdev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tmbdev/subscriptions","organizations_url":"https://api.github.com/users/tmbdev/orgs","repos_url":"https://api.github.com/users/tmbdev/repos","events_url":"https://api.github.com/users/tmbdev/events{/privacy}","received_events_url":"https://api.github.com/users/tmbdev/received_events","type":"User","site_admin":false},"created_at":"2016-10-25T18:22:31Z","updated_at":"2016-10-25T18:22:31Z","body":"On Thu, Oct 20, 2016 at 7:46 AM, Amit D. <notifications@github.com> wrote:\n\n> *ocropy barely uses the hOCR features*\n>\n> https://github.com/tmbdev/ocropy/blob/1a906e3ac/ocropus-hocr\n> https://github.com/tmbdev/ocropy/blob/1a906e3ac/ocrolib/hocr.py\n>\nocropy only contains basic physical layout analysis; experimental tools for\nlogical layout analysis, and even features such as text/image segmentation,\nnever made it into the open source release, so nothing in ocropy produces\nthose tags. Those tools take physically marked up hOCR and produce\nlogically marked up hOCR as output.\n\nWe've also used many more of the hOCR features when converting OCR training\ndatabases and OCR output from other engines into a uniform format. That is,\nmany of the hOCR tags are tags that occurred in other formats and needed a\ntranslation.\n\nTom\n"}}
{"actor":{"display_login":"tmbdev"}}