Dawn Childress

I think this issue was resolved with the work to support IIIF Image service?

Here is a cookbook recipe for a simple book manifest that has no thumbnail properties: https://iiif.io/api/cookbook/recipe/0009-book-1/. This generates thumbnails in UV 4.0.25: https://www.universalviewer.dev/#?xywh=-1565%2C-257%2C6333%2C5125&iiifManifestId=https%3A%2F%2Fiiif.io%2Fapi%2Fcookbook%2Frecipe%2F0009-book-1%2Fmanifest.json I think it was fixed with #817

I added contentState and contextualizing motivations to prezi context here: https://github.com/IIIF/api/pull/2305.

Do we want to include in the revised charter developing Search extensions?

To clarify, `unordered` is not valid on Manifests then? Is there a use case where someone would have an `unordered` behavior on a Manifest that did not apply to its...

Oh, gotcha. The current language didn't at first seem to be ambiguous, so I misread your message above. I'll take a stab at clarifying the language.

I created the selectors context and it's available here: https://iiif.io/api/registry/selectors/context.json. The updated and migrated Registry of Selectors page is here: https://iiif.io/api/registry/selectors/. We should remove or archive the old annex page....

Just commenting to reiterate that this is still an issue. Per the IIIF spec, for the viewingHint/behavior properties "The value must be an array of strings." https://iiif.io/api/presentation/3.0/#behavior.

This needs one more review and a merge - @JulieWinchester or @mixterj?

For the discussion on order of images/"which image appears on top", see the Implementation notes in this recipe: https://iiif.io/api/cookbook/recipe/0036-composition-from-multiple-images/ - just in case this question comes up re: content state