api
api copied to clipboard
IIIF
Source for API and model specifications documents (api and model)
Currently the IIIFv3 specification makes no mention of the ["Physical Dimensions Service"](https://iiif.io/api/annex/services/#physical-dimensions) that was introduced in IIIFv2. Most importantly it's missing a `type` entry in the table in section ["3.3.1...
Preview: https://preview.iiif.io/api/annex-migration-services/registry/services/ This draft PR is the start of migrating the annex/services content to registry/services. So far this: - copies the GeoJSON section over to registry per #2019 - adds...
Split from #547. __Issue:__ In order to allow the IIIF Authentication workflow to work with non IIIF Image API resources, such as audio or video resources, there needs to be...
While writing a cookbook recipe on how to use AnnotationCollections https://github.com/IIIF/cookbook-recipes/issues/309 the question arose where it is allowed to put an AnnotationCollection in a Manifest. The spec explicitly mentions an...
The various APIs will frequently refer to each other, as seen with the Presentation and Image API contexts. To avoid embedding references to contexts everywhere, JSON-LD 1.1 lets us use...
While implementing the Authentication API, I stumbled on two issues with internationalized messages: 1. **Multi-lingual/Multi-valued labels/headers/descriptions** Currently the specification does not explicitely mention that these fields can be multi-lingual and...
Assuming my reading is correct, when a token expires the most appropriate error state is `invalidCredentials` -- invalid because they have expired, not because the user is not authorized. This...
As it's a preflight request for XHR, while the following GET can redirect, the OPTIONS must return 200. This is somewhat contrary to section 3.2 of the Auth API: >...
> "an appropriated authorized" should be "an appropriately authorized" (Auth 1.0.1?)
http://iiif.io/api/auth/1.0/#tiered-access currently says: > If a server supports multiple tiers of access, then it MUST use a different identifier for each Description Resource and its corresponding Content Resource(s). Which isn't...