{"action":"created","issue":{"url":"https://api.github.com/repos/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/27","repository_url":"https://api.github.com/repos/kshawkin/Best-Practices-for-TEI-in-Libraries","labels_url":"https://api.github.com/repos/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/27/labels{/name}","comments_url":"https://api.github.com/repos/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/27/comments","events_url":"https://api.github.com/repos/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/27/events","html_url":"https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/27","id":114094243,"number":27,"title":"Coordinated OCR in BPTL","user":{"login":"smjwsk","id":1132631,"avatar_url":"https://avatars.githubusercontent.com/u/1132631?v=3","gravatar_id":"","url":"https://api.github.com/users/smjwsk","html_url":"https://github.com/smjwsk","followers_url":"https://api.github.com/users/smjwsk/followers","following_url":"https://api.github.com/users/smjwsk/following{/other_user}","gists_url":"https://api.github.com/users/smjwsk/gists{/gist_id}","starred_url":"https://api.github.com/users/smjwsk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/smjwsk/subscriptions","organizations_url":"https://api.github.com/users/smjwsk/orgs","repos_url":"https://api.github.com/users/smjwsk/repos","events_url":"https://api.github.com/users/smjwsk/events{/privacy}","received_events_url":"https://api.github.com/users/smjwsk/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2015-10-29T16:44:37Z","updated_at":"2016-10-07T13:52:41Z","closed_at":null,"body":"Most OCR Pipelines today provide coordinated OCR output which can be used for further processing. Some elements for this are in place, such as `<surface>` or `<facsimile>`, others from the analytic module, e.g. `<w>`, are missing. A usecase would be to have a common baseline format for meta-data and annotation on the text without loosing information present in machine generated OCR. Usecases like this include: Generation of derived document formats on existing TEI processing pipelines (TEI, epub...), annotation and creation of enhanced and improved versions, maybe even editions on the basis of (the cases with good) OCR. Generally, DH scholars start to request data in a suitable for their further work and libraries will want to provide."},"comment":{"url":"https://api.github.com/repos/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/comments/252257803","html_url":"https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/27#issuecomment-252257803","issue_url":"https://api.github.com/repos/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/27","id":252257803,"user":{"login":"kshawkin","id":538464,"avatar_url":"https://avatars.githubusercontent.com/u/538464?v=3","gravatar_id":"","url":"https://api.github.com/users/kshawkin","html_url":"https://github.com/kshawkin","followers_url":"https://api.github.com/users/kshawkin/followers","following_url":"https://api.github.com/users/kshawkin/following{/other_user}","gists_url":"https://api.github.com/users/kshawkin/gists{/gist_id}","starred_url":"https://api.github.com/users/kshawkin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kshawkin/subscriptions","organizations_url":"https://api.github.com/users/kshawkin/orgs","repos_url":"https://api.github.com/users/kshawkin/repos","events_url":"https://api.github.com/users/kshawkin/events{/privacy}","received_events_url":"https://api.github.com/users/kshawkin/received_events","type":"User","site_admin":false},"created_at":"2016-10-07T13:52:41Z","updated_at":"2016-10-07T13:52:41Z","body":"We might also consider whatever approach is adopted for https://github.com/TEIC/TEI/issues/1508 ."}}
{"actor":{"display_login":"kshawkin"}}