This document provides an overview of the International Image Interoperability Framework (IIIF). It discusses IIIF as a standard for presenting and annotating digital cultural heritage objects. Key points include: - IIIF allows for interoperability across institutions through shared APIs. - It provides features like deep zoom, annotation, and searching within large image collections. - IIIF is implemented through its Image API and Presentation API and has led to many applications and open source projects.

1. An Open & FAIR Technology Standard
Amsterdam – 22 November 2019
Josh Hadro
Managing Director
IIIF Consortium
@hadro | @iiif_io
International
Image
Interoperability
Framework

2. FAIR Data
Findable
Accessible
Interoperable
Reusable

3. Agenda
• What is IIIF?
• Why do we need IIIF?
• What does IIIF do?
• How does IIIF work?
• Museum case-study examples (and
others)

4. What is IIIF?
International
Image
Interoperability
Framework
(triple-eye-eff)

5. A model for presenting and
annotating digital
representations of objects
(with lots of other benefits)

6. A Community
that develops shared APIs,
implements them in software,
and exposes interoperable
content

9. Museums / Galleries
British Museum
National Gallery of Art
The J. Paul Getty Trust
The Walters Art Museum
Yale Center for British Art
Et al.
Aggregators
Artstor
CONTENTdm
DPLA
Europeana
Internet Archive
Wikimedia Foundation
State / National
Libraries
Austria
Bavarian State
British Library
Denmark
Egypt
France
Israel
Japan
Moravian Library
New Zealand
Norway
Poland
Scotland
Serbia
Wales
Qatar
United States (LoC)
Vatican
Universities and
Research Institutions
Cambridge
Cornell
Ghent
Gottingen
Harvard
Michigan
Oxford
Princeton
Stanford
Edinburgh
Toronto
Wellcome Trust
Yale
International Leaders

10. Why do we need IIIF?

11. Images are fundamental information
carriers for cultural heritage

12. But image delivery on the Web
is…
• disjointe
d
• hard
• slow
• expensiv
e
• locked
up
http://www.loc.gov/pictures/resource/fsac.1a34206/

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

14. What does IIIF do?

15. Deep zoom with large images

16. Cite and share (including regions of interest)

17. Compare images

18. Across sites

19. Collect items that belong
together
Le manuscrit 5 de la
Bibliothèque municipale de
Châteauroux, c. 1460
Folio in BVMM
Miniature in the BNF

20. Collect items that belong
together

21. Reunify

22. Search within

23. Annotate
https://courses.edx.org/courses/course-v1:HarvardX+MCB64.1x+2T2016/d16e07a5cec442eeb7cd9dfcb695dce0/

24. Guide
http://storiiies.cogapp.com/

25. Mirador instances on display at McMullen Museum, Boston College.
Enrich

26. All with the application of your
choice
Mirador Universal Viewer IA Book Reader
Qatar Digital Library
Archival papers shown in 4
different viewers.

27. IIIF A/V prototype, Distributed Digital Music Archives & Libraries Lab
… and beyond just images!

28. How does IIIF work?

29. Application Programming
Interfaces
https://commons.wikimedia.org/wiki/File:Creaci%C3%B3n_de_Ad%C3%A1m.jpg

30. Application Programming
Interfaces
https://commons.wikimedia.org/wiki/File:Creaci%C3%B3n_de_Ad%C3%A1m.jpg
APIs provide a structured way
for connecting systems

31. Application Programming
Interfaces
https://commons.wikimedia.org/wiki/File:Creaci%C3%B3n_de_Ad%C3%A1m.jpg

32. Application Programming
Interfaces

33. Application Programming
Interfaces

34. APIs enable reuse
Export & Embed in
3rd Party Apps
Data Store
Customized App
Annotation
Environments
APIs

35. APIs => Framework =>
Ecosystem
App 4App 1
Annotation &
Transcription Tools
Data Store 1 Data Store 2 Data Store 3 Data Store 4
APIs
APIs
APIs
APIs
Cross Repository Search
& Delivery Environments

36. “get pixels” via a
simple, RESTful,
web service
Just enough metadata to
drive a remote viewing
experience
Image API Presentation API
IIIF: Two Core APIs

37. Image Delivery API
http://iiif.io/api/image/2.1/

39. Presentation API
http://iiif.io/api/presentation/2.
1/
• Structure
– Collection, Item, Sequence,
Parts
• Properties
– Labels, description, license,
attribution, links

40. Image + Presentation = Object

41. Presentation
API
• Title Label
• Structure
(TOC)
• Sequence
Image
API
• Image
Data
Image + Presentation = Object

46. To support login, and
differential access to
resources.
Search within an
object, such as the full
text of a book or
newspaper
Authentication APISearch Within API
IIIF: Two More APIs

47. How do you get started
with IIIF?

48. IIIF Compatible Software

49. · Cultural institutions from across the world
· Monthly calls — 1st. Tuesday
· Example topics:
Demos of IIIF implementations from various
institutions, discussions around various topics such as
Digital Asset Management System (DAMS) needs,
projects around scholarly research, and beginner
questions about IIIF
· More info:
https://iiif.io/community/groups/museums/#ab
out
· Join the IIIF #museums channel!
Museums
Community
Group

50. How others use IIIF

51. Folger Shakespeare Library

52. https://collections.okeeffemuseum.org/object/998/
Georgia O’Keeffe Museum

53. Georgia O’Keeffe Museum

54. https://albert.rct.uk/
The Royal Collection Trust

56. https://conversations.terraamericanart.org/artnav
Terra Foundation for American
Art

57. https://conversations.terraamericanart.org/artnav

58. Vatican Library

59. https://spotlight.vatlib.it/

60. The Victoria and Albert Museum

62. The Philadelphia Museum of Art

63. Smithsonian Institute 3D

64. Clyfford Still Museum

65. Name-Entity Recognition (Royal
Academy)

66. Exquisite Corpse with Portraits

69. Hundreds of adopters
Scores of applications
Billion+ digital objects
Revolutionary promise

70. 1. State of the art functionality
2. Cheaper, faster and more efficient
3. Benefits of an international standard
4. Maximize impact, use and value of
your content
5. Be at the forefront of digital innovation
…with a global community of leaders
Why embrace IIIF?

71. 1. Expose your collections via IIIF
2. Use IIIF-compatible software
3. Ask your software suppliers to
become IIIF-compatible
4. Participate in the IIIF community
5. Join the IIIF Consortium
How to Participate

72. IIIF Communication Channels
• IIIF Website: http://iiif.io
• iiif-discuss@googlegroups.com
• IIIF Slack Team – Join at http://bit.ly/iiif-
slack
• Twitter: @iiif_io and #IIIF
• Awesome-IIIF on Github
• IIIF YouTube Channel
• IIIF Events

73. @iiif_io
iiif.io
Special thanks to Tina Shah, Tom Cramer, Michael Keller, Stu Snydman, Jack Reed,
Sheila Rabun, Mike Appleby, Tom Crane, and many others for their content and expertise in
preparing this overview.
International
Image
Interoperability
Framework