api
api copied to clipboard
IIIF
Source for API and model specifications documents (api and model)
With the potential approval of the NavPlace extension, does the section in the Annex doc on [Linking to External Services](https://iiif.io/api/annex/services/#geojson) with a section talking about geojson-ld need to be revised...
Once the physdim directory is migrated from the annex to the registry, the context url (http://iiif.io/api/annex/services/physdim/1/context.json) will change (http://iiif.io/api/registry/services/physdim/1/context.json). We'll need a redirect so we don't break existing uses of...
I had forgotten that the very DRAFTy https://iiif.io/api/annex/rest/ "RESTful Management of Source Images on a IIIF Server" is public. Although marked as a draft I think it doesn't make its...
Where the intent is, I believe, that the set of manifests in the collection is unordered, rather than anything to do with those manifests canvases. Seems like a bug in...
for prezi and image, especially given newly combined context docs are an even worse proxy for them (/ht @mixterj)
Split from #547. __Issue:__ A content resource that isn't obtained from the IIIF Image API might still have services that the client can interact with directly. There isn't an info.json...
As part of discussion about linking to the [IIIF Registry of Activity Streams](https://registry.iiif.io/) it became apparent that there will be confusion with the [IIIF Extensions Registry](https://iiif.io/api/registry) if both are called...
Discovered by Steve Baskauf at Vanderbilt, the use of SpecificResource as an `items` entry in a Range is not covered by the context. `SpecificResource` is defined only in the Annotation...
In [Image 3.0](https://iiif.io/api/image/3.0/#quality) we say: > A request for the `color` quality of an image MUST return an image [...] a request for the `color` quality MUST NOT result in...
This PR should always be in draft until it is ready for review by TRC. It exists to review the georeferencing work and trigger the preview build.
