Tom Crane

Split into #2269, propose defer this original issue for now.

Successor to https://github.com/IIIF/api/issues/557 as well

If this is a successor to https://github.com/IIIF/api/issues/557 then it needs to address the use case of marking a hyperlink as being a link to an IIIF resource. For example, if...

`IIIF Manifest for this work` `IIIF Manifest for this work` ...for visible links to be rendered, rather than `

:+1: still something that needs a recipe, whatever it looks like.

One for the Newspapers WG to bounce around @kestlund @glenrobson More discussion in https://github.com/IIIF/api/issues/1296

Target scenarios - The 99% use case; one model, one Scene, I want to _paint_ this model onto this Scene, I don't want to think about positioning the model in...

> Always looks for references to services in parent resources - this might be problematic Only allowed on top level - manifest and collection - does that make it simpler?...

The `services` formalises something the UV was doing anyway - mainly to avoid JSON bloat by repeating the same auth block 500 times on a 500-page manifest. It allowed the...

Another test fixture: https://iiif.wellcomecollection.org/presentation/b19192162 (clickthrough, declared once in full in `services`, thereafter as ``` "service": { "@id": "https://iiif.wellcomecollection.org/auth/clickthrough", "@type": "AuthCookieService1" } ```