Support `max` style image URLs from IIIF 3.0

[copumpkin]

Is your feature request related to a problem? Please describe.

I'm trying to interface with an IIIF server that considers the full URLs 400-worthy, so piffle just doesn't work properly there.

Describe the solution you'd like

Either auto-detection of IIIF version to generate the correct URLs, or let us specify which IIIF version and decide which convention to follow based on it.

Describe alternatives you've considered

String replacement on the output URLs 😭

Additional context

N/A

[rlskoeser]

Hi, @copumpkin thanks for opening the issue. Thanks to @rwood-97 there is work in progress (#25) to update piffle to support newer & multiple versions of the APIs, but I don't have a timeline for integration and release. If you have any capacity you could take that version of the code out for a spin and report back how it works for your use case.

Do you have a preference between auto-detecting the version and specifying? Do you generally know in advance which version a particular endpoint is using?

Would also love to know more about where & how you're using piffle.

[copumpkin]

Hi! I hadn't seen the PR, but I'll go check it out, thanks!

I think auto-detection would be ideal if technically feasible, since if I get passed an IIIF URL I don't know ahead of time what flavor it'll be, and that could also change over time (e.g., provider X just launched IIIF 3.0 support)

I'm building a system (hopefully open source soon enough once I get it working) to crowdsource "semantic" annotation of historical photos and IIIF comes up a lot in that domain 😄 I'm using piffle to avoid having to understand the intricacies of IIIF

[rwood-97]

Hi @copumpkin, would be great if you could test out the PR :) I did the work as part of a project that sadly has now ended so I don't have a good use case to test it out with.

[rlskoeser]

@copumpkin FYI, I just published version 0.7 of piffle, which releases @rwood-97 's work to support v2 and v3 of image and presentation APIs. There's no auto-detection yet and not much in the way of documentation yet either, but hopefully still useful — and I hope we'll get to the auto-detection at some point. Let us know if you have any feedback.