Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check IIIF-URLs behaviour #231

Open
riedde opened this issue May 18, 2022 · 3 comments
Open

Check IIIF-URLs behaviour #231

riedde opened this issue May 18, 2022 · 3 comments

Comments

@riedde
Copy link
Contributor

riedde commented May 18, 2022

In a discussion about mei metadata and image urls I got a hint about the use of IIIF- URLs

This should be reflected and documented!

@riedde riedde added this to the images, viewers, servers milestone May 18, 2022
@riedde riedde self-assigned this May 18, 2022
@bwbohl
Copy link
Member

bwbohl commented May 23, 2022

I don't think that we would have to document this in the context of Edirom-Online, but at least make sure we expect the right thing and maybe point out the MEI documentation. Does that sound plausible?

@riedde
Copy link
Contributor Author

riedde commented May 23, 2022

Yes. For me it was new and I noticed that I sometimes use this in a false way. If both works it is okay for me I thought that we just document it if a special way of use is required because of the openseadragon implementation in the edirom

@daniel-jettka daniel-jettka modified the milestones: images, viewers, servers, 1.0.0-beta.6 Jun 3, 2024
@bwbohl
Copy link
Member

bwbohl commented Jul 4, 2024

We should definitely assure the media fragment syntax works an if needed translate it to the Image API syntax.

@bwbohl bwbohl modified the milestones: 1.0.0-beta.6, 1.0.0 Sep 5, 2024
@bwbohl bwbohl modified the milestones: 1.0.0, 1.1.0 Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New
Development

No branches or pull requests

3 participants