Open jronallo opened 8 years ago
Distinction to be kept in mind is that the request is for an image, rather than a very short video.
Use Case: Use the image as a thumbnail for the video in the presentation layer.
Should be the Image API, e.g. http://example.org/video/identifier/time-slice/full/full/0/default.jpg
If using Image API form then does that also imply availability of Image Information: http://example.org/video/identifier/time-slice/info.json ?
@zimeon What kind of information in an info.json would be different between these two? http://example.org/video/identifier/time-slice/info.json http://example.org/video/identifier/info.json
http://example.org/video/identifier/time-slice/info.json == Information about Image API support for one image (any image client based on current specs can use this, does not need to know anything about A/V support)
http://example.org/video/identifier/info.json == Information about A/V API support, includes notions of time
Would the info.json for one time-slice image ever be different than the info.json for another time-slice image other than the @id? Anything else that might be good to have in a video still image info.json that isn't already in the Image API?
In theory, the different time slice images could have different parameters expressed in info.json
. In practice I suspect that for a given video they'd differ only by @id
as you suggest. Not sure what else you might include beyond plain still image except perhaps a service description somehow referring to the video context?
Description
Download still frame from video as image. Or series of frames as images. Level 3 (unless implemented in client). Output is a different type (image) which distinguishes this use case from the selection of a segment of video. Media fragment spec provides way to specify point in time / frame to extract. For bonus points: create Image API service for the frame put video identifier + region/frame as identifier of image API ?
Additional Background
Source: BL workshop notes