-
Notifications
You must be signed in to change notification settings - Fork 4
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
HTML5 Player for the access files of a MediaResource #1226
Comments
No decisions have been made regarding the identification of a player, an HTML5 player may be sufficient. |
Concerns and questions regarding a IIIF 3.0 compliant player should inform this decision. For the moment, a HTML5 should be sufficient. |
Will all manifests suddenly go from v2 to v3? UV will support v3, but unfortunately it doesn't use the context object to determine which version it is or which functions to call. I think this should be addressed in the UV collaborative sprint so that it knows, for example, to use getItems() on a v3 Canvas when getImages() is called. |
cjcolvar has been fairly diligent about addressing early IIIF 3.0 support upstream (samvera/iiif_manifest#19), so we should be in the position to identify to any server-side structural issues which prevent UV from consuming responses. |
Sorry, I meant Manifesto above... so my comment may not be relevant to this issue. UV currently supports v3, with a couple exceptions like requiredStatement and rights. |
No description provided.
The text was updated successfully, but these errors were encountered: