As the IIIF community grows, the process of developing and maintaining the specifications must take advantage of the wide range of community expertise and viewpoints. As highlighted in the IIIF Code of Conduct, the IIIF community is an inclusive, friendly and safe community, committed to openness and transparency in all interactions and activities.
The Technical Review Committee (TRC) will enable the timely review of technical proposals coming from the existing, open, community-based process while also supporting community input. Ratification of specification text will occur in a structured, ongoing way that allows remote and asynchronous participation to promote the widest diversity of review possible. The TRC will also review proposals to create new Technical Specification Groups (TSGs). The TRC will rely upon engaged consortium member representatives and community members to either attend regular calls or provide input online in order to make decisions. All issues slated for discussion will be openly announced ahead of TRC review, and all decisions will also be openly documented.
The TRC will be a step on the path to increased technical engagement–from the general community, TSGs, TRC members, and Editorial Board. Representation from Consortium members provides an additional incentive for Consortium membership.
Scope and purpose
The TRC is representative of the Consortium and the community with regards to technical matters. Its purpose is to review and ratify or reject proposals to solve technical issues in an ongoing fashion. These decisions include:
- Reviewing new specifications or updates to existing specifications, from either TSGs or the Editorial Board
- Reviewing specification cookbook entries, technical registry entries, and implementation notes
- Reviewing proposals for the formation and charters of new TSGs
Once approved by the TRC, next steps depend on other community processes not described in this document.
The membership will consist of ex officio, consortium, and community members:
- Ex Officio:
- The IIIF Managing Director
- The IIIF Technical Coordinator
- The IIIF Editors
- One (non-editor) chair of each current TSG (to be decided by the TSG, if needed, with a preference for increasing organizational and other diversity where possible)
- Each IIIF-C full member institution may nominate one technical representative
- Each IIIF-C associate member institution may nominate a technical representative, a number up to half the total number of associate member institutions
- Self-nominated technical participants from the community, to a maximum of 5 slots
The positions from the IIIF-C member institutions must be members of staff for that organization, and may serve in addition to any other members of the organization that are ex officio members of the TRC. The same person cannot fill two roles at once. TSGs should select the chair that serves as an ex officio member of the TRC to maximize the diversity of representation in the TRC at the time.
To promote regular attendance and engaged discussion, the TRC will follow guidelines for participation based on those that have been used by the W3C.
The TRC will meet monthly by teleconference for one hour, and in person at the annual IIIF Working Meeting. TRC members will be able to actively participate in TRC activities even if they are unable to attend the calls or in person meetings. The TRC meetings will be open only to members. The agendas for these meetings will be set and published openly in advance by the ex officio members. The chairing of the meeting will rotate through the ex officio members per call, and per time section of in person meetings. The notes from these meetings will be published openly after the meetings.
TRC members participate by contributing to the discussion of issues and voting on items being reviewed, via the GitHub issue tracker, either synchronously during a meeting or asynchronously. If a consortium or community member of the TRC does not participate over the timeframe of three consecutive meetings (without prior apologies for a prolonged absence), then they are not in “good standing” and their vote will not count on issues until they have participated for three consecutive meetings. Standing will be tracked by analysis of participation on the GitHub issue tracker. This requirement is to ensure continued engagement, rather than dropping in for the occasional issue of interest without understanding the context in which the decision needs to be made.
The TRC process is designed to encourage input from all community members. Issues for TRC review will come from either TSGs and their open communication channels or from the Editorial Board and its community process. Pending review items will be publicly announced in advance of TRC meetings by the meeting chair, providing an additional opportunity for community input, and there may be further discussion on community calls or other open meetings.
TRC decisions are made by general consensus, and respectful, passionate, and informed debate is welcomed. Consensus is defined as: all participants in the discussion agree (+1) or decide to abstain (+0), plus no participants actively disagree (-1). Disagreement should be accompanied by a rationale and, if possible, an alternative solution that both fulfills the use case under discussion and adheres to the design patterns at least as well as the proposed solution. All decisions are recorded and not final until 7 calendar days after their publication in the notes for the meeting, to give all members of the group an opportunity to register their opinion asynchronously.
If the group cannot reach consensus in good faith, then the decision will be made by super-majority vote (2/3rds majority of those voting). If there is no super-majority then the ex officio members will decide whether to delay the decision pending further research, or to accept the simple-majority opinion.
If any member very frequently disagrees (registers a -1 opinion) with the group such that the group does not reach consensus, and in the resulting vote there are less than 5 votes in their favor, they may be asked by the ex officio members to step down from the TRC to ensure that forward progress can be made.
Community members and consortium members representing IIIF-C associate members will rotate on and off every 18 months, with a call for self-nomination two months in advance. This ensures new voices and provides an on-ramp to technical engagement for newcomers. IIIF-C institutions will be invited to change their representative at this same time, but it will not be required. If more community participants than the number of available slots (5) self-nominate, then the ex officio and consortium members representing IIIF-C full members will make the selection with a view to maximizing the diversity of representation amongst those who have previously engaged with the specification process. Community participants may continue to participate in additional consecutive rotations so long as there are available slots to fill.
- IIIF Managing Director: Josh Hadro
- IIIF Technical Coordinator: Glen Robson
- IIIF Editors: Rob Sanderson
- IIIF Editors: Mike Appleby
- IIIF Editors: Tom Crane
- IIIF Editors: Simeon Warner
- IIIF Editors: Jeff Mixter
- IIIF Editors: Dawn Childress
- IIIF TSG - Discovery: Matt McGrattan
- IIIF TSG - Authenticaiton: Stefano Cossu
- IIIF TSG - Maps: Eliot Jordan
- IIIF TSG - Content Search: Mike Bennett
Consortium full members
- Artstor/ITHAKA: Anand Krishnan
- La Bibliothèque nationale de France: Stéphane Pillorget
- British Library: Paul Clements
- Europeana: Nuno Freire
- Folger Shakespeare Library: Mike Poston
- The J. Paul Getty Trust: Stefano Cossu
- Gottingen State and University Library: Ingo Pfennigstorf
- Harvard University: Rashmi Singhal
- Indiana University: Daniel Pierce
- Johns Hopkins University: Mark Patton
- Kyoto University Library Network: Azusa Omae
- National Gallery of Art: Ben Zweig
- National Institute of Informatics: Akihiko Takano
- National Institute of Japanese Literature: Kazuhiro Okada
- National Library of Wales: Siân Thomas
- New York University Libraries: Alberto Ortiz Flores
- North Carolina State University Libraries: Jason Ronallo
- Northwestern University Libraries: Mat Jordan
- OCLC: Shane Huddleston
- Pennsylvania State University Libraries: Adam Wead
- Princeton University Library: Trey Pendragon
- Smithsonian institution: Andrew Gunther
- Stanford University: Chris Beer
- DaSCH, Swiss National Data & Service Center for the Humanities (University of Basel): Julien A. Raemy
- University of California, Los Angeles: Kevin Clarke
- University of Edinburgh: Scott Renton
- University of Notre Dame: Jon Hartzler
- University of Oxford (Bodleian Library): Andy Irving
- University of Tokyo: Kiyonori Nagasaki
- University of Tennessee, Knoxville: Mark Baggett
- Texas A&M: James Creel
- Vatican Library: Paola Manoni
- Research Computing Group at Saint Louis University: Patrick Cuba
- Wellcome Trust: Jonathan Tweed
- Yale University: Seong-June Kim
Consortium associate members
- Max Planck Institute for the History of Science, Berlin: Robert Casties
- Research Computing Group at Saint Louis University: Bryan Haberberger
- University of Oxford: Tanya Gray
- Yale University Library: Trip Kirkpatrick
- The National Gallery: Joseph Padfield
- Biblissima - Campus Condorcet - EPHE-PSL: Régis Robineau