Background

International Image Interoperability Framework (IIIF)

In short, IIIF is a standards-based approach to serving and presenting images.

IIIF publishes two APIs:

The IIIF Image API 2.0 defines how image servers should respond to image requests
The IIIF Presentation API 2.0 defines a json format for expressing information about images and collections of images

Implementing IIIF requires three steps (as described in the IIIF Quick Start Guide)

Deploy an image server, such as Loris or IIPImage
Publish metadata that conforms to the Presentation API
Deploy an IIIF-compliant viewer, such as Mirador, OpenSeadragon, the Wellcome Player, or develop your own.

The IIIF apps & demos page has a good summary of server and viewer options with a note on their IIIF compliance.

Note – some of the manifests above are still version 1.0, but 2.0 is almost backwards compatible.

Notes of discussion at Hydra Connect, January 2014 on Hydra and IIF

DCE have created RIIIF, an IIIF-compliant image streaming rails engine.

OSullivan - a ruby gem by Jon Stroop for producing IIIF Presentation JSON manifests: https://github.com/jpstroop/osullivan

Spiiiffy - ruby gem for creating IIIF manifests from METS files: https://github.com/pulibrary/spiiiffy