IIIF Editorial Committee

The IIIF Editorial Committee works in collaboration with community groups to propose new technical specifications and to update existing ones. The Technical Review Committee (TRC) enables the timely review of these proposals.


The initial membership of the Editorial Committee was set in Memorandum of Understanding that established the IIIF Consortium in 2015.

Per the Memorandum of Understanding, the editors may nominate additional editors at any time. All current editors must agree before an invitation is issued. Editors will choose from participants within the community and/or experts willing to lend their knowledge and experience to new specifications. Opportunities to better the gender, race, and age balance of the existing editorial team will also be a consideration. New editors must be approved by the IIIF Executive Group.

There is no set number of editors, but this does not mean that the number of existing editors will not be taken into account when considering new editors. The existing editors will seek out new or additional editors when they are lacking knowledge or significant empathy for use cases in an area that the community has agreed is important.


Editors must agree to follow the IIIF editorial process, including attendance at meetings, and to the intellectual property conditions under which the specifications are published. They are responsible for confirming that these conditions are also acceptable to their employer, where applicable.

It is not expected that every editor comment on every issue, though they should make every effort to do so. Editors may be dismissed from work on a specification, or the editorial group altogether, when they fail to meet the expectations of their colleagues, as described here.

Current Membership

Change Log

Date Description
2021-03-04 Updated to include Maria, Jeff, and Dawn, update Rob’s affiliation
2018-11-12 Separated from description of editorial process
2017-03-17 Updated (@srabun, @azaroth, @zimeon, @tcramer)
2015-12-22 First release (@mikeapp, @tomcrane, @azaroth42, @jpstroop, @zimeon)