Updating meta-recipe: Transcripts, Captions, and Subtitles - General Considerations

[elynema]

Recipe info:

• Name: Transcripts, Captions, and Subtitles - General Considerations
• link: https://iiif.io/api/cookbook/recipe/0231-transcript-meta-recipe/

Correction request

There are quite a few edits being proposed by the AV Annotations TSG to update this according to the proposed new provides property and to reflect current common practice for serving transcript and caption content.

Under Transcripts:
1.2 Providing access to transcript alongside the resource.
I think this is really referring to unsynchronized display of transcription. With the proposed provides property, there could be a new recipe for a newspaper or manuscript. For AV materials, synchronized and unsynchronized transcripts can be handled with a recipe such as 'Using Transcript Files with A/V content'. This recipe does not exist and could show pointing to either timed text transcripts (ex: .vtt) or untimed text transcripts (ex: .txt or .docx).

1.3.c Providing synchronized access to transcript and resource, example in the A/V space
This currently links out to the proposed #79 Using Annotations for Timed Text. However, synchronized access can also be provided by linking out to a .vtt file (and is probably easier for IIIF clients to actually support). We should either add the use case of linking out to a .vtt in #79 or add a reference to the new recipe proposed above 'Using Transcript Files with A/V Content'

Under Captions and Subtitles:
Note, captions are often also provided as .srt files.

1.a Serving the caption file directly - 'Using Caption and Subtitle Files with Video Content' recipe will no longer be identical to 2 above, so need to remove that reference.
1.b Serving the caption file directly - Indiana serves video content via HLS and uses the same method as 'Using Caption and Subtitle Files with Video Content' recipe for captions (only the HLS part is different) , so I don't think this line is necessary. Recipe 257 doesn't mention anything about captions, just HLS content.

2. Transforming captions into annotations - It does not seem that we need to encourage IIIF implementers to convert caption files into annotations when .vtt files can be handled fine by IIIF clients. Perhaps there are other reasons?