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

Add support for IIIF Image and Presentation API version 3 #58

Open
cmhdave opened this issue Nov 13, 2019 · 9 comments
Open

Add support for IIIF Image and Presentation API version 3 #58

cmhdave opened this issue Nov 13, 2019 · 9 comments

Comments

@cmhdave
Copy link

cmhdave commented Nov 13, 2019

Both IIIF Image and IIIF Presentation APIs have their BETA 3.0 versions published (currently November 2019) and the only thing holding them back from being officially released are open source implementations of each version as per their editorial standards. As version 3 opens up the ability to create manifests for audio and video we are eager to start implementing new manifests

https://iiif.io/api/image/3.0/
https://iiif.io/api/presentation/3.0/

Manifests created should pass the official IIIF v3.0 manifest validators:

https://iiif.io/api/image/validator/
https://iiif.io/api/presentation/validator/service/

Edited to add link to change logs

https://iiif.io/api/presentation/3.0/change-log/
https://iiif.io/api/image/3.0/change-log/

@cmhdave
Copy link
Author

cmhdave commented Nov 19, 2019

As I am going through the changes in IIIF 3.0 and the way the current library is designed, I'm not entirely sure what the best way is to approach implementing 3.0. It's almost as if you need to have either a new package structure for 3.0 OR create a new major version that leaves behind v2.x in lieu of only creating v3.x manifests. Any thoughts?

@andybuki
Copy link

Hi, do you plan to implement version 3?

@ksclarke
Copy link

ksclarke commented Jun 1, 2021

Not specifically related to iiif-apis (but I'm interested in this project so I track it too), but when I implemented v3 over an existing v2 branch with jiiify-presentation, I opted for a new branch to keep the new code distinct (and to be able to create a jar for v2 and another for v3). The changes were more substantial than I first imagined they would be too, fwiw. I think doing it with feature flags (or something like that) would have been quite a task.

@ksclarke
Copy link

ksclarke commented Jun 1, 2021

Fwiw, there were some pain points at first with doing two separate builds via GitHub Actions with two non-main/master branches, but they were manageable. There are a few other gotchas too with using v2 and v3 branches instead of main (e.g., the list of contributors in GitHub's UI are built off the main branch) but nothing too onerous.

@cmahnke
Copy link

cmahnke commented Jan 5, 2022

Any news on this one?

@KonradEichstaedt
Copy link

Hi There, we are looking also to using the Java API to generate IIIF-Manifests for Version 3.0. Can please let us know if it is worth to wait until the API is available? Many Thanks, Best regards Konrad

@andybuki
Copy link

andybuki commented Oct 24, 2022 via email

@KonradEichstaedt
Copy link

Hi Andrey,

mit welcher Java Bibliothek erzeugst du die IIIF-Manifeste V3.0 als JSON-Datei?

Gruß Konrad

@andybuki
Copy link

andybuki commented Oct 25, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants