Image and Presentation 3.0 Feature Implementations

[zimeon]

The Evaluation and Testing criteria in the IIIF Editorial Process are:

In order to be considered ready for final review, new features must have two open-source server-side implementations, at least one of which should be in production. New features must also have at least one open-source client-side implementation, which may be a proof-of-concept.

We'll use this ticket to track implementations of Image and Presentation 3.0 features. If you have an implementation of v3 features, please add a comment describing them. The Image API Change Log and Presentation API Change Log describe API changes, and the latter includes description of presentation features added in v3.

[mcwhitaker]

Indiana University, in collaboration with Digirati, used IIIF specs in its implementation of a newer version of the now-retired Variations Audio Timeliner, an audio annotation and analysis tool for creating and labeling bubble diagrams. These diagrams, called Timelines, can be used to navigate music or other audio for detailed study.

The bubbles correspond to musical segments and serve as visual cues that help the quick identification of elements that recur or relate in the large-scale formal structure of a musical piece. Music instructors can provide their analyses to students, helping them develop critical listening skills. Students can also interact with the tool and create their own timeline.

The new Timeliner is a different type of IIIF client given its music teaching and learning use case. IIIF Presentation API v.3, which incorporated support for A/V content, is well suited for the representation of the Timeliner annotations.

At Indiana University, the audio content is stored in the Avalon Media System, which also provides the discovery and access control to the content. The integration of Avalon and the Timeliner is facilitated by the IIIF Presentation v3 and Auth v1 APIs. For Auth, we implemented the Probe service suggested in #1290.

We also made a standalone version of the tool available to the web at https://timeliner.dlib.indiana.edu.

The tool requires that the A/V content be accessible via the web.

[mcwhitaker]

As of version 6.5, the Avalon Media System generates a IIIF manifest for every item. The manifest is available via an endpoint accessible by adding /manifest to the item url. For instance, if your item is: https://pawpaw.dlib.indiana.edu/media_objects/qf85nb41q, the manifest is https://pawpaw.dlib.indiana.edu/media_objects/qf85nb41q/manifest.

Avalon includes in the IIIF Presentation v 3.0 manifest for the items the structural metadata created via its new Structural Metadata Editor (SME). In this implementation, we use IIIF ranges to represent the various parts of the structure of an audio or video item.

Our Standalone IIIF player react component (not yet part of the Avalon release) uses the IIIF Presentation v3 manifest to drive the media player.

[tomcrane]

The Universal Viewer implements Presentation 3. Most of this has come about through the British Library's Save our Sounds:

This means:
Collections
Manifests
Canvases with duration
Ranges addressing canvases with duration, arbitrarily nested

Taking a run through the specification, there are some features and properties that UV does not make use of, better to call out exceptions below. If it's not mentioned below, the UV supports it in a manner that qualifies as an implementation. For example, provider - UV supports this so it's NOT in the list.

There are many recipes that the UV won't support - which is a different matter. Moving all the advanced association features to recipes makes it easier for a client to be IIIF compliant.

placeholderCanvas and accompanyingCanvas - the UV does recognise accompanyingCanvas but needs a little more work on what it does with placeholderCanvas - this is ongoing. So the distinction between the two is a useful and implemented feature.

repeat behavior - has not come up as a use case yet. (auto-advance is recognised and drives behaviour described in https://docs.google.com/document/d/1ad4m48FEVUBSuKf8dkwG0_M10kQnvM9g6qVShvMuO8s/edit#)

unordered and individuals - not explicitly recognised... but then, I'm not sure that's an issue.
The UV needs more work on the behaviour of inherited behaviors... but it is using them.

facing-pages - not specially handled.

together - not implemented yet but is in backlog for BL

sequence - not yet (as in range providing an alternative sequence)

thumbnail-nav - not yet

timeMode: only trim (default) implemented.

start: not yet but want to...

supplementary - no (although I have other impls that do)

[zimeon]

Started work on table of feature support at Ann Arbor working meeting: https://docs.google.com/spreadsheets/d/1Ek2YxwpYbU--94PekRKXqTDu5TeB-55sWb7LDXC9srk/edit#gid=0

[zimeon]

Image and Presentation 3.0 have been released, per IIIF/trc#37 we concluded that there were sufficient implementations. Removing this issue from the milestone but will leave open to track perhaps.

[azaroth42]

Seems like this issue has served its purpose. If there's a desire to keep a more running list of implementations and their features, that seems like a IIIF/website issue, not IIIF/api?

Propose close.

[azaroth42]

3.0 published. Closing.