search

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

Be able to describe navigation and hierarchy #21

Open jronallo opened 7 years ago

jronallo commented 7 years ago

Description

Be able to describe navigation and hierarchy. Tracks /song within album regardless of carrier. Logical structure.

Variation(s)

Related IIIF: metadata on Range

Additional Background

Source: BL workshop notes Interest: 100%

zimeon commented 7 years ago

Seems related to the implementation of segments we saw in the Avalon demo given 2016-09-06. Example on live UI Avalon instance with what looks like separate streams for each segments is https://media.dlib.indiana.edu/media_objects/avalon:2360 -- UI plays one to the next by default.

jronallo commented 7 years ago

Is this about navigation/hierarchy between separate files/resources or is it about navigation/hierarchy within a single audio/video file? Would the solutions be different in different cases?

For instance if an album is digitized from vinyl the choice could have been made for each side to be a separate file. And each side could have multiple songs that you want to describe and navigate to. We also want to be able to describe and navigate through the structure of the album as a whole. We might also want the whole album separate between two files to play all the way through.

In another case the decision for ripping an album from CD could have been for the whole album to be one file or the album to be broken up into individual files for each song. In either case you still want to be able to navigate between songs and play the album all the way through.

We ought to be able to accommodate all of these cases.

azaroth42 commented 7 years ago

In the Presentation API there's no distinction between single and multiple resources. You could have a Range that spans a certain segment of time on a single canvas, or spans multiple canvases. Each canvas could have 0 to many resources associated with it.

So I think we can accommodate the use cases :)