The document provides a status update on technical specifications related to the IIIF community, highlighting developments such as the beta release of the Image and Presentation API 3.0 and updates on authentication and search APIs. It discusses the formation of a Technical Review Committee for managing specifications and community engagement, along with improvements in discovery and content state APIs. Emphasis is placed on internationalization, developer satisfaction, and compliance with upstream standards.

1. Technical Specification
Status Update
Michael Appleby, Yale University
Tom Crane, Digirati
Robert Sanderson, J. Paul Getty Trust
Jon Stroop, Princeton University Library
Simeon Warner, Cornell University
Wednesday, 26 June 2019, Alte Mensa, Göttingen

2. ● Current Specifications
● Image and Presentation API 3.0 Beta Release
● Authentication and Search API Updates
● Discovery
● Technical Review Committee
● Questions

3. Current API Specifications
● Image 2.1.1 - (2017-06-09)
● Presentation 2.1.1 (2017-06-09)
● Search [within] 1.0 (2016-05-12)
● Authentication [workflow] 1.0 (2017-01-19)

4. Image and Presentation API 3.0 Beta
(*Beta as of 20 June 2019)

5. Image and Presentation API 3.0 Beta
● Support for Audio/Visual Resources
● Better and More Internationalization
● Developer Happiness
● Update/Compliance with Upstream Standards
● Separated cookbook and extensions registry

6. TODO: Search and Auth. 1.0 Updates - 2020
● Pattern alignment Image and Presentation APIs
● Vocabulary alignment Image and Presentation APIs
● Minor fixes and possible enhancements
● Breaking changes - v2.0 releases

7. Change Discovery API 0.3
"Discovery for Machines"
● Output of Discovery TSG
● v0.1 2018-05 → v0.3 2019-03
● Follows ideas of ResourceSync but leverages the W3C
Activity Streams specification
● Use seeAlso to link to structured metadata
https://iiif.io/api/discovery/0.3/

8. Discovery for Humans?
● 2018 workshop at Stanford
● Plan for new Community Group
○ Use cases
○ Experiments
○ Shared metadata and transformation

9. Content State API 0.2 (real soon now)
● Formerly "Import to Viewers"
● v0.1 2018-10, v0.2 2019-02...07
● Intend to replace old "Drag and Drop" pattern with more
accessible and more general solution
● Key use case: Link from search result to a viewer
showing the relevant part of resource
https://preview.iiif.io/api/content-state-0.3/api/content-state/0.2/

10. Technical Review Committee (TRC)
1. New specifications or updates to existing
specifications, from either Technical Specification
Groups (TSGs) or the Editorial Board
2. Cookbook entries, technical registry entries, and
implementation notes
3. Proposals for the formation and charters of new TSGs
https://iiif.io/community/trc/

11. TRC - Membership and Participation
Membership:
● Ex officio (managing director, technical coordinator, editors, and a chair
from each active TSG)
● Consortium (representative from each IIIF-C full member, election from
associate members, 18 month terms)
● Community (up to 5 elected from community self-nominations, 18 month
terms)
Monthly calls, alternating timezones, and asynchronous participation.
Members must contribute to maintain good standing.

12. Agreement
Simple, 34 thumbs up!
TRC members vote with
● +1
● 0
● -1

13. Discussion
● Discussion on call
and on the github
issue
● Vote still ⅔
super-majority in
favor

14. Rejected!
Simple-majority but not a
⅔ super-majority
⇒ goes to ex officio
members to decide
In this case decided more
discussion required

15. Transparent
Everything on github (as
with other IIIF activities)
with links to issues and
changes (PRs)
Only TRC member votes
count

16. Questions?
Michael Appleby, Yale University
Tom Crane, Digirati
Robert Sanderson, J. Paul Getty Trust
Jon Stroop, Princeton University Library
Simeon Warner, Cornell University
Wednesday, 26 June 2019, Alte Mensa, Göttingen