IIIF / iiif-av

The International Image Interoperability Framework (IIIF) Audio/Visual (A/V) Technical Specification Group aims to extend to A/V the benefits of interoperability and the growing ecosystem of clients and servers that IIIF provides for images. This repository contains user stories and mockups for interoperable A/V content – contributions are welcome.

http://iiif.io/community/groups/av/

Apache License 2.0

13 stars 3 forks source link

Use cases where user has to make a choice #59

Open srabun opened 7 years ago

srabun commented 7 years ago

Description

For example:

sound files are available in multiple languages - which one does the user want to hear? also, captions in different languages (as specified by https://github.com/IIIF/iiif-av/issues/10)
there are multiple recordings of the same music score
different versions of audio - an original version and a cleaned up version

Variation(s)

(do you know of, or can you imagine, similar use cases?)

Proposed Solutions

two audio files, one in jp, one in nl intent is: user will pick the appropriate one Choice version (language property)

{
  "type": "Choice",
  "items": [
    {
      "id": "",
      "type": "Audio",
      "format": "audio/mp3",
      "language": "jp",
      "label": {"jp": "日本語", "en": "Spoken"},
      "metadata": [{"label": "Voice Actor", "value": "..."}]
    },
    {
      "id": "",
      "type": "Audio",
      "label": {"nl": "Gesproken", "en": "Spoken"},
      "language": "nl"
    }
  ]
}

Additional Background

(more about your perspective, existing work, etc. goes here.)

zimeon commented 7 years ago

For the use case where we have a video that is dubbed in two languages and has subtitles in two languages (expressed as annotation lists) then we not only need a way to specify the language associated with the video (as above) but also associated with the related annotation lists : IIIF/iiif.io#1065

The general principle is that a client SHOULD make a choice when it can but allow the user to override it. For example, start playing in the user's localization language. We understand that in certain cases this will be the "wrong" selection and that the user will have have to override, but that this will be a small subset of the user cases so a reasonable compromise.

zimeon commented 7 years ago

Question down the road is whether we might want a viewingHint to avoid the client going ahead with making an initial choice. ( @glenrobson ? )

glenrobson commented 7 years ago

Not sure how viewing hint would stop the client making the initial choice if it can see the language field in the choice (given in the example at the top).

Definitely use cases for changing language, some Welsh learns may want to listen to the Welsh but read the English. I think it would be fine for the client to default to the one that matches the current locale but client should be able to say other languages are available.

Do we need to specify which is the original language and which is the translated? Maybe could do this with metadata.