IIIF stands for International Image Interoperability Framework and is a standard to deliver images over the web and has existed since 2011. Normally, a website operator embeds an image in a website, which is then downloaded and displayed for visitors in their browsers. The vast majority of images that can be seen on the web is delivered from web servers to users in this fashion. Simple.

IIIF is a more involved way to deliver images. On the server side, it requires not only a web server, but an image server. On the user side, it not only requires a browser, but an IIIF viewer. So, why would anyone go through the hassle of inventing this standard, inventing image servers, and inventing IIIF viewers?

 

Left: Viewing a high resolution image with an IIIF viewer: zooming an panning is easy to do. The example source is: Selden Map of China, 1620–1629, Bodleian Library MS.Selden supra 105, Photo: Bodleian Libraries, University of Oxford, Link

Right: Viewing a high resolution image in your browser is a pain, as it is not optimised for zooming an panning on big images. The example source is the same as on the left.

There are some very practical benefits to delivering images conforming to the IIIF standard:

  1. Imagine you are viewing a very big image, say a 10,000×10,000 pixel scan of an oil painting. This is annoying to do through your browser: it takes a long time to download, and panning around the image is a pain. An IIIF viewer first shows a low-resolution version of the image, and only increases the resolution as the user zooms into the picture. This way, the user does not have to download the whole picture at once. Furthermore, the IIIF viewer is made to give the user a cozy zooming/panning experience.
  2. Imagine you are a museum and want to share images together with didactics and annotations online. Of course, you are free to do so, using your own HTML code. But IIIF defines a standard to write down those didactics and annotations, which will then be conveniently displayed in any IIIF viewer alongside the images. So, IIIF is a convenient way for website owners to display content without having to do any development themselves.

An example of an IIIF image with annotations, displayed using digilib. It can be accessed here. Source of the image is: Cunard Line – to all parts of the world, poster, Ulrich Gutersohn, about 1920, England. Museum no. E.1829-2004. © Victoria and Albert Museum, London

Now, of course, whenever anyone defines a standard, they have much higher goals than catering to the laziness of website operators or website visitors. Here are two more philosophical reasons why IIIF was brought into life, and the reader may judge by themselves how realistic these scenarios are:

  1. If every website has their own way to display images with didactics and annotation, I am bound to find one way that I don’t like. If the websites instead provide their images according to the IIIF standard, I can consume them using my favourite IIIF viewer.
  2. Different institutions may hold different parts of a collection, or even different parts of a single work (here is an article about the latter scenario: https://www.newyorker.com/business/currency/scattered-leaves). In a pre-IIIF world it would be a headache for any of these institutions to provide their users with a way to view the thing as a whole. However, if every institution delivers their part of the work via IIIF, then anyone can just collect all the image links, add annotations and didactics as they please, and create a continuous viewing experience.

So, here are two ways how you can join the IIIF fun as a user:

  1. Visit a website that has an embedded IIIF viewer. For example, check out this ornate map of shipping routes from 1620s on University of Oxford website, or this Harvard website having embedded the Mirador viewer to display a manuscript.
  2. Take your favourite IIIF viewer and view IIIF content in there. For example, here you can view the map from the previous point in UniversalViewer, another IIIF viewer.

The coming two parts will teach you how to impress your website visitors by delivering your very own IIIF pictures to them.

Read more: https://ascdc.sinica.edu.tw/single_news_page.jsp?newsId=2945


IIIF是「國際圖像互操作架構」的英文簡稱,它是一項在2001年成立的網絡傳送圖像標準。一般來說,圖像由網站營運營商嵌入網站中,經使用者下載後便會顯示在其瀏覽器上。網上絕大多數的圖像都是循這種方式從網絡服務器傳遞給使用者的。

IIIF是傳遞圖像的另一種複雜方式。它不僅用到網站伺服器、圖像伺服器,也需要網站瀏覽器和IIIF圖像瀏覽器(viewer)。如此複雜,為何仍被廣泛應用呢?

 

左:IIIF圖像瀏覽器能輕易放大和平移高清圖像。
示例來源:Selden中國地圖,1620–1629年,MS.Selden supra 105,照片來源:牛津大學Bodleian圖書館(鏈接
右:在普通網站瀏覽器中難以觀賞高清圖像。照片來源同左。

以IIIF標準傳送圖像有很多好處:

1.如觀看一個大檔的圖像,例10,000×10,000像素的油畫掃描,用普通網站瀏覽器的話除下載時間長,並且很難用滑鼠平移圖像。 IIIF瀏覽器的話,可先顯示圖像的低清版,而僅在使用者放大圖片時才提高清晰度。這樣使用者不必一下便下載整張圖片,更能輕易縮放和平移。

2. 博物館如欲在網上和大眾分享圖像註記,是可自行編寫HTML碼而做到,但亦可用IIIF的註記標準技術,便無需額外投放精力。

以digilib瀏覽器展示帶註釋的IIIF圖像( 鏈接)。 圖像來源:Cunard Line – to all parts of the world,海報, Ulrich Gutersohn,約1920年,英格蘭。 博物館編號 E.1829-2004。 ©倫敦維多利亞和阿爾伯特博物館

IIIF的誕生也有另外的原因:

3. 如果各個網站都以不同瀏覽器/方式來展示有註記的圖像,那麼可能讀者會不喜歡用其中一些但無法改變。但如果這些網站都運用IIIF顯示圖像,便可以讓讀者選擇用個人喜歡的IIIF瀏覽器來觀看它們。

4. 一套館藏,甚至一件藏品的不同部分可能分散在不同的機構(後一種情況可閱:https://www.newyorker.com/business/currency/scattered-leaves)。 在IIIF未被發明之前的世界,這些機構是很難讓讀者了解館藏的完整度的。 但是,如果它們都支援IIIF技術,那麼任何人只要取得所有圖像的鏈結,便可在同一圖像瀏覽器觀看和比較圖像,更能在閱時添加註釋,讀者便能享有一個完整的瀏覽體驗。

以下有兩種方式讓你也能體驗IIIF的樂趣:

1.逛逛有在使用IIIF瀏覽器的網站。例如,可試閱牛津大學網站此中國1620年代的運輸路線圖,或者在哈佛網站用Mirador瀏覽器觀看古老手稿

2.用您喜歡的IIIF瀏覽器上打開IIIF圖像看看。 例如,您可以另一IIIF瀏覽器UniversalViewer去觀賞之前介紹過的地圖

下次的兩篇文章將會介紹如何在自己的網站使用IIIF傳送和顯示圖像,讓瀏覽您網站的讀者驚艷!

閱讀更多:  https://ascdc.sinica.edu.tw/single_news_page.jsp?newsId=2945