Glen Robson
Glen Robson
Done in schema. Test with new schema
I think this would be better in the annotationTarget so it doesn't need to test the array and single: https://github.com/IIIF/presentation-validator/blob/1aaaaee6746944d69d25a7d6e747e3542bd3f0f9/schema/iiif_3_0.json#L973
Icons look OK, maybe rename the image files so they aren't the same as the spec. Fix build and approve over slack.
Add explination of Partial and text about YES, NO or Partial at the top.
I've reviewed @dlpierce and they look good to merge. Note the comment in #644 mentions jp2s but I think this only applies to jpgs through TurboJpeg.
Example v3 and v4 recipe: https://preview.iiif.io/cookbook/v4/recipe/0001-mvm-image/
Another option is to stop writting v3 recipes at a point and then start a new v4 cookbook. Gradually start converting v3 recipes and link between 3 & 4.
Should we add a section in v4 recipes to say the changes with v3? Not all recipes will have a version in 3 e.g. 3d Maybe a warning or just...
Here is a prototype for a v3 and v4 recipe: https://preview.iiif.io/cookbook/v4/recipe/0001-mvm-image/ Comments / thoughts very welcome. (Note I noted some issues in the [pull request](https://github.com/IIIF/cookbook-recipes/pull/598))
Note underlying directory structure for a v4 recipe: https://github.com/IIIF/cookbook-recipes/tree/v4/recipe/0001-mvm-image/v4 * Question what to do about a v4 only recipe? (echoing Trip's comment above) * We could move the v3 recipe...