Skip to content

Commit

Permalink
Adding motivations group
Browse files Browse the repository at this point in the history
  • Loading branch information
glenrobson committed May 15, 2024
1 parent 0c588df commit 48dc10c
Show file tree
Hide file tree
Showing 3 changed files with 123 additions and 0 deletions.
17 changes: 17 additions & 0 deletions source/_data/groups.yml
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@
label: 3D TSG #Group name
alternate_names: # name used on IIIF calendar
- 3D Technical Specification Group
- IIIF 3d TSG
description: The IIIF 3D TSG explores the addition of 3D properties into the IIIF Presentation API specifications.
link: /community/groups/3d/tsg #link to charter
type: tsg #TSG or community
Expand Down Expand Up @@ -45,6 +46,20 @@
type: community
notes: https://drive.google.com/drive/folders/1gz7OBW8JEK_WUnhLxQ7FD0vSWv9umJ31
meeting_frequency: Every four weeks, on Mondays
- id: av-motivations
label: AV Motivations TSG
alternate_names:
- AV Motivations TSG
description: The AV Motivations TSG are looking into how to identify different types of annotations related to AV material like transcriptions and closed captions.
link: /community/groups/av-motivations/
type: tsg
chairs:
- Emily Lynema (Indiana University)
- Mark Baggett (University of Tennessee)
- Jeff Mixter (OCLC)
- Nuno Freire (Europeana)
notes: https://docs.google.com/document/d/13_LvtOPkI5O1mjWgYLqjz9GS4cmdjdQjyu8WfGbL9vE/edit?usp=sharing
meeting_frequency: Every four weeks, on Tuesdays
- id: design
label: Design
alternate_names:
Expand All @@ -66,6 +81,7 @@
- IIIF for Education Community Group
- IIIF Education Community Group
- Education
- IIIF for Education
description: This group represents educators, educational institutions, and cultural heritage institutions with educational functions as a sector with a coherent set of interests for consideration in the development of IIIF standards and related technologies.
link: /community/groups/education
type: community
Expand Down Expand Up @@ -153,6 +169,7 @@
label: Cookbook
alternate_names:
- IIIF Cookbook
- IIIF Cookbook session
description: The IIIF Cookbook is a community initiative to create reusable “recipes” of common functions. #One sentence description for car
#link: /api/cookbook/ # needs to link to website to work and this isn't really a about the Cookbook page
#type: #TSG or community
Expand Down
58 changes: 58 additions & 0 deletions source/community/groups/av-motivations/charter.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
---
title: "AV Annotations TSG Charter"
layout: page
group: av-motivations
breadcrumbs:
- label: "Get Involved"
link: /get-involved/
- label: "Community"
link: /community/
- label: "Groups"
link: /community/groups/
---
{% assign group = site.data.groups[page.group] %}

# AV Annotations TSG Charter

## Introduction
Members from the [IIIF A/V Community Group][av-group] would like to propose a mechanism to more explicitly identify the nature of annotations in the IIIF Presentation API. The current [IIIF Presentation API 3.0][iiif-3] and [Web Annotation][w3c-anno] motivations do not provide clear, reliable mechanisms to inform IIIF clients how to distinguish between and present to the user annotations that represent transcripts, captions, and subtitles.

For A/V, the following potential use cases have been identified:

1. Modern media players have specialized tools to allow users to select and display captions and subtitles. A media player must be able to reliably identify which annotations in a manifest are captions or subtitles so they can be made available to users and properly displayed on top of video.
2. For a single media item there may be a set of captions with added text for the hearing impaired (indicating, for instance, that music is playing or that the doorbell is ringing) in addition to the file captioning only the spoken dialogue. In this scenario, the media player may want to automatically identify and utilize the annotation(s) that represent the accessible caption in specific situations, such as when the user mutes the volume.
3. Audio description is used to provide description of visual information for blind or visually impaired users. It generally takes the form of a secondary audio track. The IIIF viewer should be able to identify annotations that represent tracks with audio description so they can be made available to turn on via a gadget in the viewer.
4. Many media players provide the user the ability to access a transcript for an audio or video item. Annotation(s) that represent this transcript should not be displayed on top of video and should be made available to users as a distinct set (and are often available to download). The media player needs to be able to identify which annotation(s) should be presented to the user as a transcript and should be indexed for search purposes.
5. A video may carry subtitles in both the original language (ex: English) and a translation (ex: French). The media player needs to be able to identify these annotations to render on top of the video and may want to indicate to the user which is the original language of the video.

For Images, the use case currently not addressed by the existing motivations is:

1. Images of digitized newspapers, letters, manuscripts, etc. may be accompanied with transcribed text in both the original and translated language. How do you inform the IIIF viewer that these annotations refer to a transcription, or translation of a transcription, of the text present in the images, so that they can be displayed appropriately to users (ex: identified as a transcription, rather than a comment)?

## Scope
The scope of the work to be performed by the AV Annotations TSG will be limited to addressing the use cases related to transcriptions, captions, and subtitles, and translations of those items.

## Deliverables
Appropriate deliverables will depend on the recommendations produced by this group.

## References
The document [Extending Motivations Proposal: captioning, subtitling, transcribing, translating](https://docs.google.com/document/d/1G6DFWuwX9VcpCzM8kaC0E8b_-Pj5Owrzb_BzDQWZ27s/edit?usp=sharing) contains initial recommendations for new motivations and their use cases. It was developed by the IIIF A/V Community Group.

Some recipes in the cookbook are helpful to understand the difference between these motivations, especially [Transcripts, Captions, and Subtitles - General Considerations](https://iiif.io/api/cookbook/recipe/0231-transcript-meta-recipe/).

## Roadmap
* Group formation: December 2023
* Delivery of extension:
* Initial Draft: April 2024
* Final Draft: June 2024

## Communication channels:
* Calls: {{ group.meeting_frequency }} - see [IIIF Community Calendar][iiif-calendar] for details
* Email: [iiif-discuss][iiif-discuss] with subject line: \[Motivation-TSG\]
* General discussion on the [AV Slack channel][av-slack]

[w3c-anno]: https://www.w3.org/TR/annotation-model/#motivation-and-purpose
[iiif-3]: {{ site.root_url | absolute_url }}/api/registry/motivations/
[iiif-discuss]: https://groups.google.com/forum/#!forum/iiif-discuss "IIIF-Discuss Forum"
[av-slack]: https://iiif.slack.com/messages/av/details/
[iiif-calendar]: {{ site.root_url | absolute_url }}/community/groups/
48 changes: 48 additions & 0 deletions source/community/groups/av-motivations/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,48 @@
---
title: "AV Annotations TSG"
layout: page
group: av-motivations
breadcrumbs:
- label: "Get Involved"
link: /get-involved/
- label: "Community"
link: /community/
- label: "Groups"
link: /community/groups/
---
{% assign group = site.data.groups[page.group] %}

## About
Members from the [IIIF A/V Community Group][av-group] would like to propose a mechanism to more explicitly identify the nature of annotations in the IIIF Presentation API. The current [IIIF Presentation API 3.0][iiif-3] and [Web Annotation][w3c-anno] motivations do not provide clear, reliable mechanisms to inform IIIF clients how to distinguish between and present to the user annotations that represent transcripts, captions, and subtitles.

The scope of the work to be performed by the AV Annotations TSG will be limited to addressing the use cases related to transcriptions, captions, and subtitles, and translations of those items.

The group [charter][charter] specifies the deliverables and aims of the group in more detail.

## Organization

**Chairs:**
{% for chair in group.chairs %}
* {{chair}}
{% endfor %}

**Communication channels:**
* Calls: {{ group.meeting_frequency }} - see [IIIF Community Calendar][iiif-calendar] for details
* Email: [iiif-discuss][iiif-discuss] with subject line: \[Motivation-TSG\]
* General discussion on the [AV Slack channel][av-slack]

**Call notes and group documents:**
* [Group notes]({{ group.notes }})

**Call connection information:**
* Online: [Zoom](https://stanford.zoom.us/j/98998220214?pwd=RmV5ZGNpbVhnZldzc2JyN3dnZFgrdz09)

[events]: {{ site.root_url | absolute_url }}/event "IIIF Events"
[av-group]: {{ site.root_url | absolute_url }}/community/groups/av/
[iiif-3]: {{ site.root_url | absolute_url }}/api/registry/motivations/
[w3c-anno]: https://www.w3.org/TR/annotation-model/#motivation-and-purpose
[iiif-discuss]: https://groups.google.com/forum/#!forum/iiif-discuss "IIIF-Discuss Forum"
[av-slack]: https://iiif.slack.com/messages/av/details/
[slack]: http://bit.ly/iiif-slack
[iiif-calendar]: {{ site.root_url | absolute_url }}/community/groups/
[charter]: {{ site.root_url | absolute_url }}/community/groups/av-motivations/charter/

0 comments on commit 48dc10c

Please sign in to comment.