For this version, <resource name="myvideo" encodings="myvid.mp4:video/mp4;myvid.ogv:video/ogg"> how would you specify path information, if the files are not in the same folder? How about using an approach similar to frames in resources:
<resource name="myvideo" type="video"> <encoding src="/mp4path/myvideo.mp4" /> <encoding src="/ogvpath/myvideo.ogv" /> </resource> On Wed, Jan 5, 2011 at 3:22 AM, Henry Minsky <[email protected]>wrote: > Firefox and Safari both support the <video> and <audio> HTML tags, but > Safari only supports MPEG encoding, and Firefox only > supports Theora (a royalty-free video encoding format). > > I've got a component for DHTML video playback, which looks like > > <html5videoview src="yourmovie.mp4"> > > But you don't want to hardcode the filename, because you need to choose at > runtime which file to use for the browser. > > The browser kernel has to detect which browser is being used, and look up > which encoding format(s) it supports. That code probably belongs in the > browser kernel. > > And then maybe for a given "video" resource, we probably want some > structured way to specify a list of different files/URLs and what their > encoding is (encoding can be guessed from the file extension if we stick to > some convention). There's suggested MIME types for mp4 and theora > > oga audio/ogg .ogv video/ogg > > .mp4 video/mp4 > > .mov video/quicktime > > .mp3 audio/mpeg > > I'm just not getting a clear idea of how this should be organized. Do we > extend the <resource> tag to support specifying multiple encodings? > > You could have a list of files, CSS style, whose encodings is implicit: > > <resource name="myvideo" encodings="myvid.mp4;myvid.ogv> > > or fully specified > > <resource name="myvideo" > encodings="myvid.mp4:video/mp4;myvid.ogv:video/ogg"> > > Then you could use that resource name in a video view, and it would do the > browser dispatch for you > > <html5videoview resource="myvideo"> > > whereas if you want to force the URL you specify > > <html5videoview src="myvideo.mp4"> > > > Thoughts? > > > > > > > > > -- > Henry Minsky > Software Architect > [email protected] > > >
