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

Segmentation by time for download #4

Open jronallo opened 8 years ago

jronallo commented 8 years ago

Description

Client should be able to request an arbitrary segment of a resource by time for download.

This is distinct from:

Allow temporal dimensions by importing the media fragment spec (SMPTE) into the Media API. See: https://www.w3.org/TR/media-frags/#naming-time

Thus the URL pattern might be something like: identifier/t1,t2/xywh/size/?/default.avi

It has implications on an info.json equivalent, where pre-configured temporal "tiles" might be available for download, either by track/chapter/semantic section or simply by subdividing the content evenly.

Additional Background

Difficult to do on the fly, so likely a "level 3" feature

Source: BL workshop notes

azaroth42 commented 8 years ago

This, to me, is the actual AV API, rather than just HTTP.

jronallo commented 8 years ago

So this is about download of segments and not playback? To support download of segments similar to the Image API it would require downloading just media fragment (time and xywh). Does anyone know of an existing server that can do this? How feasible is it to create such a segment for download within the request-response cycle? It seems that video manipulation like this is usually the kind of thing that is done asynchronously in a background process.

Does this need to support any arbitrary segment and region of media at the moment a user requests it or only those that are advertised through an info.json or manifest as having been pre-created?

azaroth42 commented 8 years ago

So ... pre-configured snippets could be built ahead of time, as per sizes in the Image API. Should be forwards compatible to a time when we can do it, the same way that level 0 implementation of sizes and tiles is forwards compatible to having dynamic extraction from the image.