-
Notifications
You must be signed in to change notification settings - Fork 54
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
Non Image thumbnails #1176
Comments
AV call 08/22: As points to a specific format, it would point to a particular encoding of a video rather than the multi-format choice or canvas. Challenge then is what to do for clients that only support one of the encodings, and how to describe the resource in sufficient detail that the client can determine which to use. Currently no documentation about the implication of more than one thumbnail. No service available for AV, compared to Images. |
Getty AV discussion: All of the thumbnails should be equally useful, such that if you pick any one of them depending on the current client environment, it should be sufficient. Otherwise 👍 |
May help to see some examples of what this would look like with different and multiple formats to have something more to comment on. |
Possible examples:
|
Also, an audio thumbnail for a manuscript is good for accessibility purposes. |
Toronto WG Plenary: 👍, modulo a question about using Also, needed to clarify via disucssion that:
|
Thumbnail is always a list is pretty clear in the spec:
|
For audio only canvases, the only "thumbnail" available might be a short audio clip rather than an image. Similarly for video, the thumbnail might be a video.
I propose to allow these as thumbnails, and thus require both id and type on a thumbnail resource.
The text was updated successfully, but these errors were encountered: