Difference between revisions of "IIIF Framework"
From CETAF Identifiers Wiki
Roger Hyam (Talk | contribs) (Created page with "Part of IIIF Pages It can be daunting for a newcomer to reach an understanding of what IIIF is as it consists of a series of technical and social components working...") |
Roger Hyam (Talk | contribs) |
||
| Line 16: | Line 16: | ||
Here we will mainly discuss IIIF in the narrow sense of the APIs and software but these are just the concrete manifestation of the collaboration between individuals and institutions who maintain them. There are currently six distinct APIs. Below is a brief outline of what they do and how they interact with each other. The specifications themselves are quite accessible and provide full descriptions of each API. | Here we will mainly discuss IIIF in the narrow sense of the APIs and software but these are just the concrete manifestation of the collaboration between individuals and institutions who maintain them. There are currently six distinct APIs. Below is a brief outline of what they do and how they interact with each other. The specifications themselves are quite accessible and provide full descriptions of each API. | ||
| − | + | :'''Recommendation:''' The most recent versions of the APIs are Version 3.0 for Image and Presentation and Version 1.0 for Authentication, Search and Change Discover. Adoption of these most current versions of APIs is recommended. Earlier versions are not discussed here. | |
| − | + | ||
Back to [[IIIF| IIIF Home]] | Back to [[IIIF| IIIF Home]] | ||
Revision as of 12:02, 29 September 2022
Part of IIIF Pages
It can be daunting for a newcomer to reach an understanding of what IIIF is as it consists of a series of technical and social components working together towards three goals (from the IIIF website):
- To give scholars an unprecedented level of uniform and rich access to image-based resources hosted anywhere.
- To define a set of common application programming interfaces that support interoperability between image repositories.
- To develop, cultivate and document shared technologies, such as image servers and web clients, that provide a world-class user experience in viewing, comparing, manipulating and annotating images.
The four components that make up IIIF in the broad sense are:
- Technical standards in the form or Application Programming Interfaces (APIs).
- Software applications including image viewers, server components and scripts that run in the background to publish image data.
- The IIIF Consortium (IIIF-C), a membership organisation that provides steering and sustainability for the IIIF community. It comprises more than 40 Founding Members who have committed to support the growth and adoption of IIIF. It has a small paid staff and is most visible in organising workshops, conferences and training events.
- The IIIF community which includes the adopters, users and developers of IIIF standards and software. By extension, dear reader, that includes you.
Here we will mainly discuss IIIF in the narrow sense of the APIs and software but these are just the concrete manifestation of the collaboration between individuals and institutions who maintain them. There are currently six distinct APIs. Below is a brief outline of what they do and how they interact with each other. The specifications themselves are quite accessible and provide full descriptions of each API.
- Recommendation: The most recent versions of the APIs are Version 3.0 for Image and Presentation and Version 1.0 for Authentication, Search and Change Discover. Adoption of these most current versions of APIs is recommended. Earlier versions are not discussed here.
Back to IIIF Home
