Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal for adding 'timed-text' in the Text Granularity Extension #117

Open
glenrobson opened this issue Jul 14, 2023 · 4 comments
Open
Assignees
Labels
Milestone

Comments

@glenrobson
Copy link
Member

Links

Background and Summary

(Copied from pull request)

Captions and subtitles for video objects can be made available via the IIIF Presentation API by using annotations on the canvas that contains the media file. For reference, see the Section "Captions and Subtitles" for the recipe "Transcripts, Captions, and Subtitles - General Considerations".

Just like the OCRed text of a newspaper can be provided via annotations with spatial coordinates on a images, captions and subtitles may be provided as annotations with temporal coordinates (a cookbook recipe for providing captions and subtitles as annotations is planned for the IIIF cookbook).

The Text Granularity Extension allows one to indicate the level of text granularity for an annotation (block, line, etc.), but currently it does not contain a suitable granularity value for the case of captions and subtitles, whose text granularity is neither paragraphs of sentences. The text granularity of captions/subtitles follows standard subtitling guidelines in terms of reading speed, number of lines in each subtitle, line length (number of characters), minimum and maximum subtitle duration, and minimum interval between two consecutive subtitles.

Proposed Solution

In conclusion, the text granularity of captions and subtitles is specific to these resources, and this proposal consists in adding the text granularity level 'timed-text' to the levels defined by the extension.

@glenrobson glenrobson added this to the July 2023 milestone Jul 14, 2023
@zimeon
Copy link
Member

zimeon commented Jul 19, 2023

I'm still struggling with whether this is a granularity like line, block etc. or really something orthogonal. I think I lean toward @nfreire's argument that this is comparable (one wouldn't also say it was line or block) but I think this needs some more discussion as a group to get agreement before moving forward.

Naming -- why not timed rather than timed-text? We don't say block-text.

If/when this moves forward we should update date of addition (currently 2023-03-07) in the document history block before merge.

@nfreire
Copy link

nfreire commented Jul 19, 2023

Regarding the naming, "timed-text" is an established generic term in the audio-visual community to refer to captions, subtitles, etc.

@triplingual
Copy link

Where I resolve the orthogonality in my head is that the other granularities are dimensions of text, and time is a dimension of AV. Also that the "text" in AV, if spoken or signed, say, may not have lines or grafs but will often be captioned in multi-word units.

But AV text can be captioned in words even if the text is audio or gestural, so I do also think that some discussion needs to go into refining these text granularities to account for transcriptions of visual text in a video (e.g. Barbara Kruger's or Jenny Holzer's video work) and gestural language (with dimensions that are not necessarily graf/line/word/glyph).

@glenrobson
Copy link
Member Author

Issue 117 (Proposal for adding 'timed-text' in the Text Granularity Extension)

+1: 1 [triplingual]
0: 4 [julsraemy kirschbombe regisrob zimeon]
-1: 0 []
Not TRC: 0 []
Ineligible: 0 []

Result: 1 / 5 = 0.20

Issue is rejected

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants