Tom Crane

Discovery perspective (via @jronallo): > ...one scenario which might come up is that a v2 manifest with seeAlso metadata may become static once we have reached the tipping point of...

I have already started rolling that ball for thumbnails.

IIIF AV Meeting suggestions: * Canvas on Canvas * Language selection - does this move out of the spec? - no * Ranges, manifest.items, thumbnail strips, `behavior:sequence` * Processing Collections...

Yes.

 This would be a very poor user experience for a Real World Object... and would be an equally poor user experience as a single IIIF Manifest.

Equivalent to 2.1 fixtures https://iiif.io/api/presentation/2.1/example/fixtures/32/manifest.json https://iiif.io/api/presentation/2.1/example/fixtures/33/manifest.json https://iiif.io/api/presentation/2.1/example/fixtures/34/manifest.json

Equivalent to 2.1 fixture https://iiif.io/api/presentation/2.1/example/fixtures/61/manifest.json

Equivalent to 2.1 fixtures https://iiif.io/api/presentation/2.1/example/fixtures/43/manifest.json https://iiif.io/api/presentation/2.1/example/fixtures/44/manifest.json https://iiif.io/api/presentation/2.1/example/fixtures/45/manifest.json https://iiif.io/api/presentation/2.1/example/fixtures/46/manifest.json https://iiif.io/api/presentation/2.1/example/fixtures/47/manifest.json https://iiif.io/api/presentation/2.1/example/fixtures/48/manifest.json

Is this a cookbook recipe? In the spec it would be no more than that clients should follow redirects?

Propose transferring to cookbook repo issues.