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

HTML5 Player for the access files of a MediaResource #1226

Closed
hackartisan opened this issue May 10, 2018 · 5 comments · Fixed by #1383
Closed

HTML5 Player for the access files of a MediaResource #1226

hackartisan opened this issue May 10, 2018 · 5 comments · Fixed by #1383
Assignees
Labels

Comments

@hackartisan
Copy link
Member

No description provided.

@escowles escowles added the ready label May 21, 2018
@hackartisan hackartisan changed the title Display the access files of a MediaResource Player for the access files of a MediaResource May 22, 2018
@escowles escowles added groomed and removed ready labels May 29, 2018
@jrgriffiniii jrgriffiniii added ready and removed groomed labels Jun 4, 2018
@jrgriffiniii
Copy link
Contributor

No decisions have been made regarding the identification of a player, an HTML5 player may be sufficient.

@jrgriffiniii
Copy link
Contributor

Concerns and questions regarding a IIIF 3.0 compliant player should inform this decision. For the moment, a HTML5 should be sufficient.

@jrgriffiniii jrgriffiniii reopened this Jun 4, 2018
@jrgriffiniii jrgriffiniii changed the title Player for the access files of a MediaResource HTML5 Player for the access files of a MediaResource Jun 4, 2018
@sdellis
Copy link
Member

sdellis commented Jun 5, 2018

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.

@jrgriffiniii
Copy link
Contributor

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.

@sdellis
Copy link
Member

sdellis commented Jun 5, 2018

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.

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

Successfully merging a pull request may close this issue.

6 participants