Tom Crane

Addressed in https://github.com/IIIF/api/pull/2115 Commit: https://github.com/IIIF/api/pull/2115/commits/fc9da657eef34ad06ce33875a8f7e591ac7e55f4

Not a spec suggestion (I don't think) but an observation. The current Auth spec is opinionated that it doesn't care _how_ your access control works for jpegs, mp4s and tiles...

Not sure how these are connected yet but it feels like they could be - https://github.com/IIIF/iiif-stories/issues/138 Is the mechanism for info discovery the same as the one for authed JSON...

ACTION @tomcrane to ask question on W3C privacy CG issues about sending cookies with `fetch()` and what the future of that is wrt third party cookie elimination.

Hi @scossu Yes, your summary is correct. User U's browser address bar shows `https://a.edu/viewer`; it will therefore not send any cookies when it requests https://b.edu/image.

Update on where this being discussed W3C Privacy Community Group: https://github.com/privacycg/storage-access/issues/72 Minutes of meeting - https://github.com/privacycg/meetings/blob/main/2021/telcons/04-22-minutes.md Chrome - Privacy Sandbox: https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support/discussions/8

And update on experimental implementations using storage access API: https://tomcrane.github.io/iiif-auth-client/ This talks to three different server implementations Source code: Client - stripped down version of original auth: https://github.com/tomcrane/iiif-auth-client/tree/simplified_v1 Client: stripped...

Address in 2.0

Addressed in https://github.com/IIIF/api/pull/2115 Commit: https://github.com/IIIF/api/pull/2115/commits/f911383dfc241283b9997600fd876361959ee052

Icons in the table could maybe reference https://iiif.io/api/presentation/3.0/#a-summary-of-property-requirements rather than redefine the symbols?