Support for IIIF Image API and IIIF Presentation API

[coret]

I'm raising my comment on commit to an issue, just to be on the safe side in terms of expectations.

When I look at the code, like

makemyflix/nuxt/composables/useIsIIIF.ts

Line 3 in b419231

/https?:\/\/[^/]+(?:\/[^/]+)*\/[^/]+\/(full|square|\d+,\d+,\d+,\d+|pct:\d+,\d+,\d+,\d+)\/(full|max|!?\d+,!?\d+|pct:\d+)\/!?(\d{1,3})\/(default|color|gray|bitonal)\.(jpg|tif|png|gif|webp|jp2)/;

I see only support for the IIIF Image API at this moment in time.

In TD's quotation 2394-1 it reads "Uitgangspunt is dat we de basis ook geschikt maken voor IIIF."

As stated in Requirements for Collection Management Systems we encourage heritage organisations to provide their media using the IIIF Image API and the IIIF Presentation API. Where the IIIF Image API deals with the images, the IIIF Presentation API deals with the metadata of the images in so-called Manifests. Of interest might also be FAQ for IIIF and Linked (Open) Data. Example of an Manifest shown in a standard IIIF viewer: https://viewer.zb.uzh.ch/mv/index.php?manifest=https://www.goudatijdmachine.nl/omeka/iiif/3/17779/manifest

I hope the Manifests also come into play in this project?! Some things to consider: while the IIIF Presentation API specifies the JSON-LD format for the metadata, the more "descriptive" metadata (title, author, genre, province, colorscheme, material, ...) is not standardized. Ideally, the manifest per image is generated (statical/dynamic) based on the linked-data of the heritage organisations.