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

Describe media type, aspect ratio and resolution #19

Open jronallo opened 8 years ago

jronallo commented 8 years ago

Description

Describe media type, aspect ratio and resolution. e.g. if it's 4/3 or 16/9 aspect ratio

Variation(s)

Properties on info.json.

Additional Background

Source: BL workshop notes Interest: 100%

jronallo commented 8 years ago

My first reaction is to ask which of this information can't be determined after the load event on an HTML5 video? This won't load the whole video but just enough to get metadata to determine the mimetype, duration, video height/width, etc. https://www.w3.org/2010/05/video/mediaevents.html

I can see the need though to get this information via a JSON API as other clients than a browser might need to know this in advance of taking some other actions.

zimeon commented 8 years ago

The key question here is whether we need an info.json similar to the Image API. I think @jronallo's comment that this is likely useful for a client to know what to do is a driver, but also other use cases might demand an info.json (or equivalent), e.g. specifying thumbnail (#16), rights information (#22 and see http://iiif.io/api/image/2.1/#rights-and-licensing-properties), and related services (see http://iiif.io/api/image/2.1/#related-services).

jwd commented 8 years ago

There may also be a need to get at properties of a video that HTML5 cannot provide, e.g. I believe that mediaWidth/mediaHeight provide intrinsic display width/height in CSS pixels but not actual pixel dimensions and aspect ratio, which may differ due to non-square pixels, anamorphic video, etc.

azaroth42 commented 8 years ago

Noted on AV call that there are cases when the correct rendering dimensions and the source dimensions are different. Would need both of them to correctly display the resource.

See: https://en.wikipedia.org/wiki/Anamorphic_format

jronallo commented 8 years ago

Would the info.json for a video also have to take into account different streams and describe each separately as well as separate information about the format (container).