Open mikeapp opened 4 years ago
I've got a comment from Hugo Manguinhas, a colleague at Europeana, who said it would be nice if the documentation would be a bit less focused on (OCR-style) semi-structured sources. This could be done by just adding one line next to the example with https://example.org/iiif/aeneid/book1/transcription-line2
, saying that the pattern may also be used with full-text files and selectors upon them, not only semi-structured files.
👍 I can work with the editors to add this example and perhaps an AV example after the TRC process completes. (They're non-normative changes so can go through the eds.)
@mikeapp this would be great!
+1: 35 [Siani81 ahankinson aisaac andrewgunther awead azaroth42 cubap dismorfo emulatingkat gigamorph glenrobson hadro irv jbhoward-dublin jonhartzler joshuago78 jronallo jtweed julsraemy jwd kzhr markpatton mattmcgrattan mcwhitaker mejackreed mikeapp mixterj regisrob rentonsa rsinghal scossu sredick tomcrane tpendragon zimeon] 0: 0 [] -1: 0 []
Super majority is in favor, issue is approved
AkihikoTakano Siani81 ahankinson aisaac andrewgunther awead azaroth42 cjnishioka cubap dismorfo emulatingkat gigamorph glenrobson hadro irv jbhoward-dublin jonhartzler joshuago78 jronallo jtweed julsraemy jwd kzhr markpatton mattmcgrattan mcwhitaker mejackreed mikeapp mixterj regisrob rentonsa rsinghal scossu sredick tomcrane tpendragon zimeon
aeschylus beaudet ipf jpstroop knagasaki tonyNLS
AkihikoTakano
Links
Background and Summary
The IIIF Text Granularity Technical Specification Group was formed to examine how to express the granularity of text annotations associated with IIIF images, such as the output of OCR or human transcription.
Proposed Solution
The TSG determined that the need could be satisfied by use of a single property (
textGranularity
) applied to individual annotations. A survey of OCR software resulted in the identification of a number of common text granularity levels, which are also defined in the document.The TSG determined that a standalone IIIF API would not be required; instead, the community extension mechanism introduced in IIIF Presentation API 3 would be used for this feature. As the document is the result of a formal TSG process, it will be hosted in the IIIF namespace. As a community extension, the document will not be semantically versioned.