Introduction to the International Image Interoperability Framework

International Image Interoperability Framework

Tom CramerChief Technology StrategistStanford University Libraries @tcramer

InternationalImageInteroperabilityFramework

@iiif_io www.iiif.io

Ben AlbrittonMike ApplebyTom CramerJon StroopRob SandersonStu SnydmanSimeon WarnerIIIF.io@bla222@mikeapps@tcramer@jpstroop@azaroth42@stusnydman@zimeon@iiif_io

http://projectmirador.org/demo/#347d4952-871e-414d-94a3-66e148b5c999http://parker.stanford.edu/parker/actions/page_turner.do?ms_no=2IIhttp://collections.stanford.edu/images/bin/detail?cid=413&fn=1http://libimages.princeton.edu/osd-demo/?feedme=pudl0123%2F8172070%2F01%2F00000001.jp2

https://purl.stanford.edu/hs631zg4177http://labs.cogapp.com/iiif/index.html#d91dc2c1-b523-40c9-b9d5-047bbd1d54c2

1

Images are fundamental information carriers for cultural heritage


Lewis Chessmen in the British Museum, Page of Beineke MS 109 from Yale2

Yet, we hear the following from research & memory organizations.


Lewis Chessmen in the British Museum, Page of Beineke MS 109 from Yale3

I am locked into my image delivery software


Id like to start with a few statements many of us in the library community have made about our image and collection delivery environment, and wonder if any of you have had similar thoughts.4

I need a newer, faster image server(and I cant spend much time or money on it)


I want deep zoom(on mobile)


I want to allow users to visually compare objects in the collection


with objects from other collections


and regions of those imagesI want to make it easy for my users to cite and share my images


I want to allow visitors to annotate my images online


I want to allow embedding of my images in blogs and web pages


... without losing control of them


And I shouldnt have to invent any of it.


In short, digital image delivery istoo hardtoo slowtoo expensivetoo disjointedtoo ugly

and we all suffer because of it.


Cultural heritage, memory & research institutions suffer.Software developers suffer.Users suffer.14

There is a better way...


Cultural heritage, memory & research institutions suffer.Software developers suffer.Users suffer.Budgets suffer!

15


An idea is born at dinner after DMS Tech Meeting #3 among the BL, Oxford and Stanford: if it works for Manuscripts, why cant the same principles and some of the same tools also work for all image based resources. Idea is diagrammed on the (paper) tablecloth. March 9, 201116

IIIF VisionCreate a global framework by which image-based resources (images, books, maps, scrolls, manuscripts, musical scores, etc.) from any participating institution can be delivered in a standard wayvia any compatible image serverfor display, manipulation andannotation in any application, to any user on the Web.


IIIF Vision, continuedwith tens of millions of image-based resourcesbacked by a consortium of world-leading cultural heritage and research institutionssupported by a rich and growing suite of software toolsincorporating the best of current image delivery technology, and leveraging Web standards


InteroperabilityTechnology ContextSpaceTimeUsers


So What Is IIIF?


Three things: 1.) APIs2.) growing suite of compatible software3.) community of adopters20

A Community that develops Shared APIs,implements them in Software, and exposes interoperable Content



Global Participation


International LeadersState & National LibrariesAustriaBSBBritish LibraryFranceDenmarkEgyptIsraelNew ZealandNorwayPolandQatar SerbiaVaticanWalesResearch InstitutionsC2RMF (France)Cornell UniversityThe GettyJohns Hopkins Univ.Harvard UniversityOxford UniversityPrinceton UniversityStanford UniversityUniversity College DublinWellcome LibraryYale UniversityProjectsBiblissimae-codicesTPENTextGridAggregatorsArtstorDPLAEuropeanaInternet Archive

MuseumsBritish MuseumNational Gallery of Art (US)YCBA

Technology FirmsCogAppDigiratiKlokan Technologies


International LeadersState & National LibrariesAustriaBSBBritish LibraryFranceDenmarkEgyptIsraelNew ZealandNorwayPolandQatar SerbiaVaticanWalesResearch InstitutionsC2RMF (France)Cornell UniversityThe GettyJohns Hopkins Univ.Harvard UniversityOxford UniversityPrinceton UniversityStanford UniversityUniversity College DublinWellcome LibraryYale UniversityProjectsBiblissimae-codicesTPENTextGridAggregatorsArtstorDPLAEuropeanaInternet Archive

MuseumsBritish MuseumNational Gallery of Art (US)YCBA

Technology FirmsCogAppDigiratiKlokan Technologies


The IIIF ConsortiumWhereas interoperable technology for digital delivery of image-based resources is fundamental to research, scholarship and the transmission of cultural knowledge, the undersigned institutions hereby agree to establish and manage the International Image Interoperability Framework Consortium (IIIFC).

organized June 17, 2015.


IIIF-Discuss Membershttps://groups.google.com/forum/#!forum/iiif-discuss


A world of silos & duplicationEvery site a silo ( no interoperability)Every app a one-off (overhead to code and keep)Every user forced to cope ( many UIs, little integration)


The repositories and applications providing access to Digital Medieval Manuscripts in todays environment are heavily siloed, with access to each repository provided through one off applications. This is a microcosm of the wider world of access to image based scholarly resources. 27

Welcome to Silo-ville

Grain elevators, Caldwell, Idaho, by Lee Russell, 1941. http://www.loc.gov/pictures/resource/fsac.1a34206/


APIs enable reuse


APIs to access image and description from a repository enable access to content from other applications and systems for viewing or analytics (transcription, annotation, e.g.) Some of this data could be reimported to the repository for reuse by others (e.g., transcriptions). 29

APIs -> Framework -> Ecosystem


If multiple repositories supported the same APIs for access to images, metadata and annotations, one can envision the beginnings of a framework with shared application code across different sites, and interoperable image-based resources, enabling simultaneous access to multiple scholarly repositories through a single interface. 30

get pixels via a simple, RESTful, web service Just enough metadata to drive a remote viewing experience

Image APIPresentation APIIIIF: Two Core APIs


31

Image Delivery APIhttp://iiif.io/api/image/2.0/


We started on common software stack, but quickly shifted to an API32

Presentation APIhttp://iiif.io/api/presentation/2.0/

StructureCollection, Item, Sequence, PartsPropertiesLabels, description, license, attribution, links


We started on common software stack, but quickly shifted to an API33

Developed out of the Digital Manuscript Interop WorkProvides a lingua franca for modelling image & text-based digital resources Based on Linked Data: Web and annotation-friendly!Shared Canvas Data Model


34

http://www.shared-canvas.orgBased on Shared Canvas Data Model


Image APIPresentation API

Image + Presentation = Object


36

Image APIPresentation API

Presentation API

Title LabelStructure (TOC)SequenceImage APIImage DataImage + Presentation = Object


37

To support login, and differential access to resources. Search within an object, such as the full text of a book or newspaperAuthentication APISearch APIIIIF: Two More APIs in Beta


38

Compatible Software

IIP Image

IIP Moo Viewer

digilib

FSI ServerMiradorInternet Archive Book Reader

Image ServersImage ClientsImage Apps

FSI ViewerLeaflet JS


39

Tweets on Recent IIIF News


Distinct ConcernsFind, Use, Analyze, AnnotateWant: Mix & Match, Best of Breed

ScholarsTool MakersRepositoriesBuild useful tools and appsWant: Users & resources

Host, Preserve (and Enrich) ResourcesWant: Use of Resources, Enriching services, Enriched content


The repositories and applications providing access to Digital Medieval Manuscripts in todays environment are heavily siloed, with access to each repository provided through one off applications. This is a microcosm of the wider world of access to image based scholarly resources. 41

Some Demonstrations



Biblissima: MSS of France

Le manuscrit 5 de la Bibliothque municipale de Chteauroux, c. 1460

Folio in BVMM Miniature in the BNF


Folio is in BVMM: Bibliotheque Virtuelle de Manuscrits medievauxMiniature was eventually acquired by the Royal Library and is now in the colleciton of the BNF43


Shared Canvas at Work


Folio is in BVMM: Bibliotheque Virtuelle de Manuscrits medievauxMiniature was eventually acquired by the Royal Library and is now in the colleciton of the BNF45


Diva.js & Music Annotations


http://ddmal.github.io/diva.js/try/iiif-highlight-pages/47

Klokan Tech Georeferencer


Working at Scale

https://purl.stanford.edu/hs631zg4177


https://purl.stanford.edu/hs631zg4177http://library.stanford.edu/blogs/digital-library-blog/2015/11/adventures-oversized-imaging-digitizing-omi-kuni-ezu-jin-jiang

Omi Kuni-ezu Japanese tax map from 1837. Drawn in the round; one is meant to stand in the center and then read it in any direction one facesNo longer possible with fragile, nearly 200-year old artifact

The map measures 11x17Wayne is 64

The scanned map is34,342 x 22,939 pixels787.8 mega pixels1.27 GB file size Composite of 158 individual images

49

What's in it for Me?



1.) Rich Image DeliveryFast, rich zoom & pan delivery of images, with options for size, scale, region of interest, rotation, quality and format.

2.)Plug and Play SoftwareUse any IIIF-compatible software for viewing, comparing and manipulating images from any IIIF-compatible site. Swap parts of the stack at any time, or run multiple components in parallel at once. Benefits


3.) Publish Once, Reuse OftenDeliver images from your own site for manifold uses; host a single copy and let others embed. Obviate the need to transfer images to other for local loading, processing or delivery.

4.)Remix ContentAssemble and use image-based resources from across the Web, regardless of source. Compare pages, build an exhibit, or create a virtual collection of items from different sites. Benefits


5.) Cite & ShareIIIF APIs give long-term, portable views onto images or any regions of an image. Cite an image with confidence, or share it for reference by othersor yourself in a different environment.

6.)Annotation-friendlyNative compatibility with the W3C annotation working groups model, Open Annotation. Comment on, transcribe, mark up and more any image-based resource using the Webs architecture. Benefits


7.) Support for Attribution & Access ControlBuilt in API calls support attribution and access control.

8.)Join a Global NetworkJoin a worldwide network of image suppliers making content available in a common framework. Tap a growing suite of software tools and platforms. Maximize the use of your images on the Web. Unlock new potential with interoperability. Benefits


1) Rich image delivery2) Plug and play server and client software3) Publish once, reuse often4) Remix content from others5) Cite and share6) Annotation-friendly7) Support for attribution and access control8) Join a global networkBenefits


Why IIIF (in 140 Characters or Less)


What Is an Interoperable Resource?DiscoverableViewable via APIsInteractive and Manipulable (for tools, analytics)Citable / ShareableMash Up-ableAnnotation-readyWith attribution, license and links (back to the image in local context)


Photo: Jeffrey Emanuel Thanks to Harvards Fogg Museum and Rashmi SinghalNew Possibilities


Here is how Harvard has envisioned IIIF might enable new forms of research and scholarship. What can you imagine for the future for exposing content, new applications and compelling use cases? 58

@iiif_io@tcramer


http://projectmirador.org/demo/#347d4952-871e-414d-94a3-66e148b5c999http://parker.stanford.edu/parker/actions/page_turner.do?ms_no=2IIhttp://collections.stanford.edu/images/bin/detail?cid=413&fn=159

Introduction to the International Image Interoperability Framework

Technology

Transcript of Introduction to the International Image Interoperability Framework