Thomas, then the HTML5 controls don't make sense, in my opinion, as the defeat the purpose of content negotiation. It's hard for me to take that specification seriously anymore.
You could have a single video resource URI and choose the representation format based on Accept headers. You need to have explicit media type metadata in your example, then it should be enough to implement this approach: <http://videos.example.org/#video> a ma:MediaResource ; ma:title "Sample Video" ; ma:description "Sample Description" ; ma:locator <http://ex.org/video> ; dct:hasVersion <http://videos.example.org/#video.mp4> , <http://videos.example.org/#video.ogv> . <http://videos.example.org/#video.mp4> ma:format <http://mediatypes.appspot.com/video/mp4> . <http://videos.example.org/#video.ogv> ma:format <http://mediatypes.appspot.com/video/ogg> . Martynas graphityhq.com On Thu, Dec 5, 2013 at 8:31 PM, Thomas Steiner <to...@google.com> wrote: > Hi Milorad, > > Unfortunately content negotiation in the HTTP sense is not an option with > HTML5 video, as the "content negotiation" in a sense is taken care of by the > browser. In my initial mail, check the link on the @currentSrc attribute. If > you want to support all browsers on all platforms and device types, you have > to specify several sources in different encodings. So you almost always end > up with several media resources for the "same" video, hence my original > question… > > Cheers, > Tom > > > -- > Thomas Steiner, Employee, Google Inc. > http://blog.tomayac.com, http://twitter.com/tomayac > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.12 (GNU/Linux) > > iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom.hTtP5://xKcd.c0m/1181/ > -----END PGP SIGNATURE-----