- From: Conrad Parker <conrad@metadecks.org>
- Date: Fri, 18 Sep 2009 19:14:37 +0900
- To: Raphaël Troncy <Raphael.Troncy@cwi.nl>
- Cc: Media Fragment <public-media-fragment@w3.org>, Jack Jansen <Jack.Jansen@cwi.nl>, Yves Lafon <ylafon@w3.org>
2009/9/18 Raphaël Troncy <Raphael.Troncy@cwi.nl>: >>> - RESOLUTION: Content-Range <dimension> [':' <unit>] ' ' <real start >>> time> >>> '-' <real end time> '/' <total dimension> is the syntax to be used for a >>> Range Request for the temporal dimension >> >> just noticed: only the response header should include the "/<total >> dimension>" portion, not the request header. > > Yes, since it is the Content-Range header, this is in the response. I have > updated the RESOLUTION page to clarify that. It now reads: > > * The WG resolved on 2009/09/17 that the syntax for expressing a Range > request (using the HTTPBis clarification for having custom units), for the > temporal dimension, is: > > Range: <unit> '=' <start time> - <end time> > > while the response will be: > > Content-Range: <dimension> [':' <unit>] ' ' <real start time> '-' <real end > time> '/' <total dimension> > > See > http://www.w3.org/2008/WebVideo/Fragments/wiki/WG_Resolutions#Media_Fragment_Headers > and complain if it's wrong :-) great, thanks! I've updated the time range examples at: http://www.w3.org/2008/WebVideo/Fragments/wiki/HTTP_Examples please let me know if I missed any :) Conrad. > Cheers. > > 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.cwi.nl/~troncy/ > >
Received on Friday, 18 September 2009 10:15:17 UTC