Platform team's IIIF project homepage: https://www.mediawiki.org/wiki/Core_Platform_Team/Initiatives/IIIF_API

Adding Platform Engineering as Platform Team Workboards (Initiatives) was archived and as open tasks should have an active project tag

@WDoranWMF Will, could you clarify in what sense this ticket is "invalid" ?

For years people have identified adding managed support within MediaWiki for the IIIF image API and associated IIIF manifest API as the best (and a comparatively cheap) open-standards way to provide robust tile-based access to large and very large images hosted on Wikimedia platforms, our very best highest-resolution content, often the most celebrated 'crown jewels' of GLAM collaborations, to support applications like eg ZoomViewer for interactive exploration without massive downloads, and to make possible interoperability with other providers using IIIF across the world, to underline WM projects as a serious repository for institutions to release content to, so that it can be reused alongside and interoperatively with content from principal institutions around the world.

Now I understand that short-term priorities can come and go, and that while IIIF support may have been identified 18 months ago as a particularly valuable 'quick win' for Wikimedia, it may be that there is now no current activity being done or immediately intended on it.

But the need and value of tile-based access to largest images is not going to go away, nor the value of interoperability with ever-growing amounts of IIIF applications, tools, and external content.

So even if there is no current work being done, nor perhaps immediately on the horizon, would it not make sense to keep this ticket open as the top-level organising ticket for thinking about IIIF, and and for how support for it could/should ultimately (and comparatively easily in fact) be added ?

This ticket is tagged with Platform Engineering only; I assume that Platform Engineering does not plan to investigate.
If folks see a need for "top-level organizing" (e.g. because of working in this field), then I'd say a case should be made to create a dedicated project tag instead.