Introduction to the International Image Interoperability Framework (IIIF)
2 likes907 views
The document serves as an introduction to the International Image Interoperability Framework (IIIF), detailing its vision to standardize the delivery of image-based resources across various institutions globally. It outlines the functionalities of several IIIF APIs, including Image, Presentation, Search, and Authentication APIs, aimed at improving the access, manipulation, and annotation of digital content. The document also emphasizes community involvement and the roadmap for IIIF API specifications, along with examples of prominent institutions implementing IIIF solutions.
![https://example.edu/{id}/info.json
{
"@context": "http://iiif.io/api/image/2/context.json",
"@id": "https://libimages1.princeton.edu/loris/ex.jp2",
"protocol": "http://iiif.io/api/image",
"height": 7200,
"width": 5204,
"profile": [
"http://iiif.io/api/image/2/level2.json",
{
"formats": [ "jpg", "png", "gif", "webp" ],
"qualities": [ "default", "bitonal", "gray", "color" ],
"supports": [ "canonicalLinkHeader", "profileLinkHeader", "mirroring", "rotationArbitrary" ]
}
],
"sizes": [
{ "height": 225, "width": 163 },
{ "height": 450, "width": 326 },
{ "height": 900, "width": 651 },
{ "height": 1800, "width": 1301 },
{ "height": 3600, "width": 2602 },
{ "height": 7200, "width": 5204 }
],
"tiles": [
{
"scaleFactors": [ 1, 2, 4, 8, 16, 32, 64, 128 ],
"width": 1024
}
]
}](https://image.slidesharecdn.com/2017-10helsinkiiiiftutorial-171030182608/85/Introduction-to-the-International-Image-Interoperability-Framework-IIIF-58-320.jpg)
![Content
Canvas
Sequence
Manifest
Collec1on
IIIF Presentation API
“The objective of the IIIF Presentation API is to provide
the information necessary to allow a rich, online viewing
environment for primarily image-based objects to be
presented to a human user [...]. This is the sole
purpose of the API and therefore the descriptive
information is given in a way that is intended for
humans to read, but not semantically available to
machines. [... It] explicitly does not aim to provide
metadata that would drive discovery of the digitized
objects.”
— http://iiif.io/api/presentation/2.1/#objectives-and-scope](https://image.slidesharecdn.com/2017-10helsinkiiiiftutorial-171030182608/85/Introduction-to-the-International-Image-Interoperability-Framework-IIIF-63-320.jpg)
![{
label: "The institution of civil government"
metadata: [
{ label: "Author", value: ["Benjamin Hoadly"] }
]
…
}
Content
Canvas
Sequence
Manifest
Collec1on](https://image.slidesharecdn.com/2017-10helsinkiiiiftutorial-171030182608/85/Introduction-to-the-International-Image-Interoperability-Framework-IIIF-69-320.jpg)
![{
label: "The institution of civil government"
metadata: [
{ label: "Author", value: ["Benjamin Hoadly"] }
]
…
}
{
label: "The XYZ Collection"
manifests: [
…
]
}
Content
Canvas
Sequence
Manifest
Collec1on](https://image.slidesharecdn.com/2017-10helsinkiiiiftutorial-171030182608/85/Introduction-to-the-International-Image-Interoperability-Framework-IIIF-70-320.jpg)
![Endangered Archives Programme
Hosted by the British Library, example Armenian text Ոսկեայ Դուռն Դպրատան
[Voskeay durn dpratan], 1699
● http://eap.bl.uk/archive-file/EAP180-1-1-30
● in UV:
http://eap.bl.uk/archive-file/EAP180-1-1-30#?
c=0&m=0&s=0&cv=13&xywh=-102%2C112%2C2337%2C2266
● can also drag-and-drop into Mirador: http://projectmirador.org/demo/](https://image.slidesharecdn.com/2017-10helsinkiiiiftutorial-171030182608/85/Introduction-to-the-International-Image-Interoperability-Framework-IIIF-104-320.jpg)
Introduction to the International Image Interoperability Framework (IIIF)
- 1. Introduction to the International Image Interoperability Framework Simeon Warner https://orcid.org/0000-0002-7970-7855 (Director of IT for Library Linked Data and Repository Architecture, Cornell University Library, USA) National Library of Finland Kirjastoverkkopäivät (Library Network Days), Helsinki, Finland, 2017-10-26, 14:30-16:00
- 2. Credits – There are no original IIIF slide decks! ● These slides follow most closely the presentation of the IIIF Tutorial at Open Repositories 2017 (Brisbane, Australia) given in collaboration with Mike Appleby Jon Stroop, Sheila Rabun & Tom Cramer ● Introduction slides taken from a set last arranged by Tom Cramer ● They also include content from many others including Rob Sanderson, Tom Crane, ...
- 3. Agenda ● Introduction to IIIF ● Overview of IIIF APIs ● API Specifications Roadmap ● IIIF Implementations & Demonstrations ● IIIF Community ● Discussion: Do try this at home
- 6. But image delivery is… …too hard …too slow …too idiosyncratic …too disjointed …too ugly …and we all suffer because of it.
- 7. What ?
- 12. …across different sites Yale Center for Bri.sh Art: Na.onal Portrait Gallery (London) Tudor Project
- 22. What ?
- 23. IIIF Vision Create a global framework by which image-based resources (images, books, maps, scrolls, manuscripts, musical scores, etc.) …from participating institution can be delivered in a standard way …via compatible image server …for display, manipulation and annotation in application, …to user on the Web.
- 24. IIIF Vision, continued • with of image-based resources • backed by a consor1um of • supported by a rich and growing suite of • incorpora1ng the , and
- 25. So what is IIIF?
- 26. A Community that develops Shared APIs, implements them in Software, and exposes interoperable Content
- 27. A Community that develops Shared APIs, implements them in Software, and exposes interoperable Content
- 31. Community 1. Cambridge, Sept 2011 2. The Hague, April 2012 3. Edinburgh, July 2012 4. Paris, May 2013 5. Copenhagen, February 2014 6. London, October 2014 7. Washington DC, May 2015 8. Ghent, November 2015 9. New York City, May 2016 10. The Hague, October 2016 11. The Vatican, June 2017 12. Toronto, September 2018 • A/V Technical Specifica1on Group • Discovery Technical Specifica1on Group • Manuscripts Community Group • Museums Community Group • Newspapers Community Group • Sooware Developers Community Group Working Group Mee1ngs since 2011 Community Groups 12 30+ 6 par1cipants on open community calls every 2 weeks
- 33. A Community that develops Shared APIs, implements them in Software, and exposes interoperable Content
- 34. 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)
- 36. APIs -> Framework -> Ecosystem
- 38. Use Case Driven Process
- 39. IIIF APIs Core: ● Image API – access to bits of images and enough technical metadata to use them ● Presentation API – information about how sets images should be displayed and related, contains display metadata and may contain links to semantic metadata Also: ● Search API – Search within an object ● Authentication API – Tie with authentication system
- 41. IIIF Image API
- 50. https://example.edu/{id}/3930,550,980,2630/,670/0/default.jpg Many Size Options: ● w, ● ,h ● !w,h ● w,h ● pct:n
- 58. https://example.edu/{id}/info.json { "@context": "http://iiif.io/api/image/2/context.json", "@id": "https://libimages1.princeton.edu/loris/ex.jp2", "protocol": "http://iiif.io/api/image", "height": 7200, "width": 5204, "profile": [ "http://iiif.io/api/image/2/level2.json", { "formats": [ "jpg", "png", "gif", "webp" ], "qualities": [ "default", "bitonal", "gray", "color" ], "supports": [ "canonicalLinkHeader", "profileLinkHeader", "mirroring", "rotationArbitrary" ] } ], "sizes": [ { "height": 225, "width": 163 }, { "height": 450, "width": 326 }, { "height": 900, "width": 651 }, { "height": 1800, "width": 1301 }, { "height": 3600, "width": 2602 }, { "height": 7200, "width": 5204 } ], "tiles": [ { "scaleFactors": [ 1, 2, 4, 8, 16, 32, 64, 128 ], "width": 1024 } ] }
- 63. Content Canvas Sequence Manifest Collec1on IIIF Presentation API “The objective of the IIIF Presentation API is to provide the information necessary to allow a rich, online viewing environment for primarily image-based objects to be presented to a human user [...]. This is the sole purpose of the API and therefore the descriptive information is given in a way that is intended for humans to read, but not semantically available to machines. [... It] explicitly does not aim to provide metadata that would drive discovery of the digitized objects.” — http://iiif.io/api/presentation/2.1/#objectives-and-scope
- 64. Shared Canvas Data Model / Web Annotation Data Model
- 65. Shared Canvas Data Model / Web Annotation Data Model Transcription Annotation
- 69. { label: "The institution of civil government" metadata: [ { label: "Author", value: ["Benjamin Hoadly"] } ] … } Content Canvas Sequence Manifest Collec1on
- 70. { label: "The institution of civil government" metadata: [ { label: "Author", value: ["Benjamin Hoadly"] } ] … } { label: "The XYZ Collection" manifests: [ … ] } Content Canvas Sequence Manifest Collec1on
- 71. Other Properties ● Descriptive Properties (label, metadata, description, thumbnail) ● Rights and Licensing Properties (attribution, license, logo) ● Technical Properties (viewing direction, viewing hints, width, height, ...) ● Linking Properties (related, see also, start canvas, within, ... ) ● Paging Properties (first, last, next, total)
- 72. Other Types ● Annotation ● Annotation List ● Layer ● Range Content Canvas Sequence Manifest Collec1on Annota1on Annota1on List Layer Range
- 74. Coming Soon: IIIF A/V & Presentation 3.0 ● British Library “Save our Sounds” grant from Mellon Foundation ● Add a time dimension to the Canvas model ● Change to W3C Web Annotation Data Model (from Open Annotation) ● Late 2018?
- 75. IIIF Content Search API http://iiif.io/api/search/1.0/
- 76. IIIF Content Search API ● http://iiif.io/api/search/1.0 ● Specification for searching within annotations in a single IIIF resource -- implements ^F like functionality
- 80. Who is using the Search API? ● The British Library ● University College Dublin ● National Library of Wales ● The Wellcome Trust ● North Carolina State University ● 34+ institutions investigating or developing support
- 84. Live search example ● Wellcome Library ○ Origin of Species (1st ed.) -- https://wellcomelibrary.org/item/b1802922x ○ Short link https://goo.gl/BVJjs6 ○ E.g. “finches” or “fitness” Note that the IIIF Search API doesn’t specify how the search interface is presented to the user, it specifies the back-end mechanism by which the client can query annotation content on any IIIF Search API compatible server.
- 85. But what about discovery? ● Search API provides only search over annotations within IIIF resources ● Discovery TSG working on ways to support discovery of IIIF resources ○ http://iiif.io/community/groups/discovery/charter/ ● 4 areas of work ○ 1. Crawling and Harvesting (recently agreed split into 2 subsections) ○ 2. Content Indexing ○ 3. Change Notification ○ 4. Import to Viewers
- 87. IIIF Authentication API ● http://iiif.io/api/auth/1.0/ ● v1.0 released January 19, 2017 ● (18 months from first public draft) Doesn’t do authentication per se but provides an interaction pattern allowing existing authentication infrastructure (CAS, OAuth, etc.) to be used to control access to IIIF resources
- 88. IIIF Authentication API Specification describes how to ● From within a viewer, initiate an interaction with an access control system so that a user can acquire the credentials they need to view restricted content ● Give the client just enough knowledge of the user’s state with respect to the content provider to ensure a good user experience (including providing alternate images)
- 89. Authentication patterns Login ○ The user will be required to log in using a separate window with a UI provided by an external authentication system. Click through ○ The user will be required to click a button within the client using content provided in the service description. Kiosk ○ The user will not be required to interact with an authentication system, the client is expected to use the access cookie service automatically. External ○ The user is expected to have already acquired the appropriate cookie, and the access cookie service will not be used at all.
- 91. Login
- 92. Click-through
- 93. IIIF Authentication API implementations ● British Library ○ In copyright material ○ Staff access ○ Single user access within the building ● The Wellcome Library ● Getty ○ Staff access off site to private material ○ On site for copyright ● Auth Playground: ○ https://iiifauth.digtest.co.uk/ ○ paste manifests into e.g. http://universalviewer.io/examples/
- 94. HTTPS and mixed-content All of the IIIF specs work over either HTTP or HTTPS (though you shouldn’t ever use authentication with HTTP) BUT, plain HTTP and HTTPS do not play well together. Browsers block mixed- content, see e.g. ○ https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content and ○ https://www.jack-reed.com/2017/05/23/the-case-for-serving-your-iiif-content-over-https.html HTTPS – Just do it! Everyone should.
- 96. API Specifications Roadmap ● Image and Presentation APIs 2.1.1 – 2016-05-12 ● Authentication API 1.0 – 2017-01-19 ● Image and Presentation APIs 3.0 (Open Annotation to Web Annotation, support for A/V) – feature freeze 2017-12, beta draft 2018-05, publish fall 2018 if there are sufficient implementations Later: ● Search API 2.0 – will need updates from Open Annotation to Web Annotation to match Presentation 3.0 ● Auth API 1.1 – with a view to controlling modifying events as well as read ● REST & A/V bitstream APIs – deferred for the time being
- 99. A Taste of the IIIF Universe 335,000,000+ items
- 103. https://musiclibs.net/manifests/2e04e357-5225-4899-ae7c-823baf12f8af/?q=janacek
- 104. Endangered Archives Programme Hosted by the British Library, example Armenian text Ոսկեայ Դուռն Դպրատան [Voskeay durn dpratan], 1699 ● http://eap.bl.uk/archive-file/EAP180-1-1-30 ● in UV: http://eap.bl.uk/archive-file/EAP180-1-1-30#? c=0&m=0&s=0&cv=13&xywh=-102%2C112%2C2337%2C2266 ● can also drag-and-drop into Mirador: http://projectmirador.org/demo/
- 105. IIIF Community
- 106. IIIF Community Landscape ● Manuscripts ● Museums ● Newspapers ● Software Developers ● Audio/Visual ● Discovery ● Text Granularity ● Libraries ● Museums ● Research Institutions ● Archives ● Galleries ● Aggregators ● Cogapp ● Digirati ● Klokan Technologies ● LUNA Imaging ● OCLC - ContentDM ● Synaptica ● Zegami ● 4Science ● Etc. ● 47 institutional members Open Source Software ● Mirador ● Universal Viewer ● OpenSeadrgon ● Loris ● IIPImage Subject Experts
- 107. Institutional Adoption http://iiif.io/community/ IIIF Adopters Survey (2017): Presi 2.x Image 2.x Presi 2.x Image 2.x Image 1.x Image 1.x Presi 1.x Presi 1.x Auth Search Authentication Search Image 2.x Presi 2.x Production Development Investigating
- 108. IIIF Community Groups http://iiif.io/community/groups • Manuscripts • Newspapers • Museums • Software Developers
- 109. Technical Specification Groups As needs arise within the community, new technical specification groups are formed, currently: • IIIF A/V • IIIF Discovery • IIIF Text Granularity New use cases considered as IIIF evolves: • https://github.com/IIIF/iiif-stories
- 110. IIIF Consortium (IIIF-C) http://iiif.io/community/consortium • 47 institutional members • Sustainability and steering for IIIF • Organizational structure: • Executive Committee – core founding members, high level direction • Coordinating Committee – active leaders for week to week activities • Editorial Group – writes API specifications • Funds two staff positions: • Community Coordinator (Sheila Rabun) • Technical Coordinator (Glen Robson) • Additional Founding Members – through 2017
- 111. Consortial Business ● Hiring a technical coordinator ● Opening up new tiers of membership in 2018 ● Seeking partners ○ Software firms ○ Contractors & consultants ○ Training ○ Complementary projects & associations ○ Please join the IIIF Consortium
- 112. Partnerships and Projects • OpenJPEG improvement project • Grant-funded projects: • Newspapers in Hydra (IMLS) • Avalon Media System (IMLS) • Save our Sounds (Mellon) • DHSI Summer Institute 2018 • American Art Collaborative consulting pilot
- 113. Emerging Trends • Increasing adoption & experimentation • STEM imaging, publishing, DH • Improving documentation for implementers and end users • Lowering the barriers to adoption
- 114. IIIF to go … and more!
- 116. Europeana IIIF Task Force Timeframe: February to June 2017 Led by: Austrian National Library Purpose: Identify current trends and tendencies towards IIIF by the Europeana content providers. Europeana has adopted IIIF but a large portion of the Europeana Network is unaware and unsure of IIIF. Output: Recommendations Report
- 117. Communication Channels • http://iiif.io/community • IIIF-Discuss email list • Recurring calls • Slack • Twitter @iiif_io #IIIF • GitHhub: h@p://github.com/iiif
- 118. Where to Learn More • IIIF YouTube channel • GitHhub: h@p://github.com/iiif • Awesome-IIIF List https://github.com/IIIF/awesome-iiif • Annual in-person events: http://iiif.io/event • Working Meetings • Conferences • Email : srabun@iiif.io
- 120. Discussion: Do try this at home