api
api copied to clipboard
IIIF
Source for API and model specifications documents (api and model)
There should be a registry for licenses and rights statements. Related to presentation but not dependent on a new version.
There are lots of implementations that add real value to the IIIF environment. No reason to not include directly in the spec.
Clients seem to default currently to a black background for a canvas, but there's no reason for that to be the case. For a dark image, a white background might...
(Splitting from #1296) In order to allow appropriate representation of a human readable label for the point on a timeline, calendar or map, it would be advantageous for the content...
From @tomcrane while working on Auth: _"Search is missing some types? And defines `match` which isn't used."_
Captions and subtitles for video objects can be made available via the IIIF Presentation API by using annotations on the canvas that contains the media file. For reference, see the...
I posted this request on the Mirador project first, but it seems to be relevant to the Presentation API specification: https://github.com/ProjectMirador/mirador/issues/3475 As an editor of IIIF collections, one would like...
This was originally raised with OpenSeaDragon in the following issue: https://github.com/openseadragon/openseadragon/issues/2321 Currently the IIIF specification states that the [rounding method is implementation specific](https://iiif.io/api/image/3.0/implementation/#3-tile-region-parameter-calculation). This can cause problems particularly with a...
The anchor for `4.4. Language of Property Values` seems to be the only one that does not include the section number (`44`): https://iiif.io/api/presentation/3.0/#language-of-property-values ... which partially breaks the direct link...
We should delete the service SHOULD have a profile, as these are now mostly in `type`. Rob and Mike believe that this is not backwards incompatible and could thus be...