Tom Crane
Tom Crane
Consider a source image with pixel dimensions 300,300 and a IIIF v3 image service. If the request is `/full/^!400,400/..` then the server can only return an image if the `max_scale`...
**UV version:** All I suspect this supersedes #132 @nicolasfranck mentioned in IIIF Slack: > the universalviewer now only supports version 0.9, and neglects version 1.0 despite the fact that is...
For many users, the URI of the manifest/canvas they are looking at is meaningless. But for others, it's really important to get access to this. See https://github.com/IIIF/iiif-stories/issues/74 and similar. Prominent...
(WIP for discussion on Auth TSG Call 26 April 2022) Preview: https://preview.iiif.io/api/1290-auth-probe-service/auth/2.0/
From @ksclarke in Slack: From the properties table at https://iiif.io/api/auth/1.0/#service-description it looks like label is required. But once one gets down to the Kiosk and External patterns we see: >...
This issue tries to summarise the different kinds of resources the IIIF Auth 2.0 Spec needs to consider, and how they are requested. We use the following terms: - a...
Auth 1.0 assumes that the user's relationship with access-controlled resources is decided by credentials carried by cookies. Even in Auth 1.0 this is not an absolute dependency; the server is...
Regardless of where https://github.com/IIIF/api/issues/1959 goes, it seems that windows that open and close themselves without user interaction are going to be frowned upon as issuers of cookies or other credentials...
Auth 1.0 assumes that the client's credentialled requests for content resources are made with cookies. This isn't a 100% requirement - the auth spec would work just as well if...
I had intended to do these separately but the PRs would have been so tortuous and conditional that it would have been hard to read. Preview: https://preview.iiif.io/api/auth2-2035-drop-clickthrough/auth/2.0/ #2035 - remove...