Skip to content

IIIF AV

Adam J. Arling edited this page Mar 29, 2017 · 6 revisions

IIIF A/V spec in it's current state

Community Group A/V Page
http://iiif.io/community/groups/av/
The central hub for IIIF A/V community information and resources.

Slack Channel
https://iiif.slack.com/messages/av/details/
Follow the latest ongoing dialogue and discussions pertaining to IIIF A/V development.

Group Documents
https://goo.gl/kNwsZq
Categorized documents pulling information from Slack channel discussions and elsewhere. A good resource for reviewing recent meeting notes, project roadmaps, implementation helpers, and sample materials.

Presently IIIF A/V's two main areas of focus are:

  • Providing access to the bitstreams of the audio and video content.
  • Integration with and extension of the existing Presentation API to accommodate its appropriate rendering.

The Audio and Video Content APIs will mirror the existing Image API in function - they provide interoperable access to temporal and spatial segmentation and transformation of the content to enable its use and reuse in multiple contexts.

This has the same division as the Image API between access to the bits and a JSON-LD description of the features provided by the service.

Development Roadmap

  • Q2 2016: Initial workshop, group formation
  • Q3-4 2016: Use Case discussion and research
  • Q1-2 2017: Alpha draft of Presentation API 3.0 recommendations to support A/V
  • Q3-4 2017: Beta draft of Presentation API 3.0 recommendations to support A/V, Alpha Audio/Video Content APIs
  • Q1-2 2018: Alpha2 Audio/Video Content APIs
  • Q3 2018: Beta Audio/Video Content APIs, V3.0 Presentation API with validators, implementations
  • Q4 2018: V1.0 for Audio/Video Content APIs with validators, implementations

Issues/Ideas about implementing IIIF A/V in Avalon/Hyrax

Client Side

  • Select/utilize an accessible, universally supported media player which can consume IIIF A/V's manifest.
  • Identify new use cases derived from expanded manifest information.
  • Identify data items in updated manifest object which may break current player implementation.

(These generally apply to sections below)

Server Side


How IIIF A/V could be implemented in Avarax

Description goes here...


How IIIF A/V could be implemented in Avalon 6.x

Description goes here...