- From: Raphaël Troncy <raphael.troncy@cwi.nl>
- Date: Tue, 09 Feb 2010 15:09:16 +0100
- To: Conrad Parker <conrad@metadecks.org>
- CC: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Media Fragment <public-media-fragment@w3.org>
Hi Conrad, > for this part (which only relates to how a client acts on a #t=), I > don't think it's necessary for the Media Fragments spec to say how a > user agent actually retrieves the data for a given media-type. This is > really dependent on that media-type; it may involve one or more > byte-range requests (eg. in the two schemes you mention for Ogg), or > it may involve loading auxiliary resources which describe where to get > various bits required for a time offset (eg. for quicktime adaptive > streaming or MS smooth streaming), and these may then involve requests > of many different resources that make up the media. Basically my point > is that the specific mechanism depends on both what the media-type > specifies and what the client is capable of, and doesn't belong in > this section of the Media Fragments spec. > > It might be simpler to just say that if the client is capable of > seeking in a resource, then the #t= indicates to the client that it > should seek to that time -- and perhaps we can even word that > unambiguously enough to be normative. Could you please add a paragraph in the Section 5.2.1 (in a note?) that says more or less that? Thanks. Raphaël -- Raphaël Troncy EURECOM, Multimedia Communications Department 2229, route des Crêtes, 06560 Sophia Antipolis, France. e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com Tel: +33 (0)4 - 9300 8242 Fax: +33 (0)4 - 9000 8200 Web: http://www.eurecom.fr/~troncy/
Received on Tuesday, 9 February 2010 14:10:14 UTC