IIIF Validation

[thehabes]

Tie into the IIIF Validators to check on the URIs supplied by users. Objects used in the Navplace Viewer should pass validation in order to be used, and notify the user of the validation error otherwise.

Consider specific lenience around the @context property.

[glenrobson]

Hi Brian, do you have particular examples which are failing? Cheers

[thehabes]

Hi @glenrobson !

No, nothing failing. The Navplace Viewer just simply does not take advantage of the fact there is a validation endpoint. For the navPlace workflow, IIIF Validation should be a part of that workflow.

For example, the geolocator should not mint a navPlace value for invalid IIIF resource types, as the resulting derivative which includes navPlace would then also be invalid. At a minimum, the user should be warned about this even if we continue to make the derivative.

I have gotten clear user feedback that the software should continue for resources with invalid or missing @context. In a perfect world, the derivative produced would make sure the @context is mended. That's the bit about lenience for this property.