Tom Crane
Tom Crane
...along the lines of info.json for image API What motivations do I support? What options for granularity do I support (see, #758 #TBC) What parameters do I support? This allows...
To support #758 and complex client requirements, a search server might provide transcriptions by: - page - area - paragraph - line - word Clients should be able to specify...
These changes would be a breaking change for v3 of Search, but they allows for static implementations A Server MUST state that it has ignored parameters defined in the Search...
In anticipation of future revisiting of #780 We dropped `box` or `region` from the first version of the Search spec for the reasons in that issue. Now that Presentation 3...
Clients like UV and Mirador may wish to support both Auth 1.0 and Auth 2.0 at the same time - there are extant Auth 1.0 servers out there. Implementation notes...
## Summary If browsers won't send third party cookies, cross-domain IIIF interoperability for access controlled content is broken. ## Detailed Version Interoperability for IIIF is about _third party contexts_; where...
(raised after discussion with @jennpb) **Summary** An institution publishes IIIF resources. On its own site, with its own user interface / viewer(s) / etc, it can capture as much visitor...
In Auth 1, the client deduced that a redirect might have happened by observing that the URL it asked for is not the `id` of the info.json it eventually sees...
This issue is a continuation of #2158. The [current draft of auth](https://preview.iiif.io/api/1290-auth-probe-service/auth/2.0/#21-probe-service) says, in [section 2.1](https://preview.iiif.io/api/1290-auth-probe-service/auth/2.0/#21-probe-service): > * The info.json must always be its own probe service, and is always...
This issue does not address a published spec, but does propose simplifying an approach that has been in drafts of auth (and experimental implementations) for a while. For an image...