W3C home > Mailing lists > Public > public-media-fragment@w3.org > September 2009

Re: time range request/response syntax (Re: minutes of 2009-09-17 F2F meeting, Day 1)

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Sat, 19 Sep 2009 15:48:24 +1000
Message-ID: <2c0e02830909182248m76a7e3ceh5022234162de12f@mail.gmail.com>
To: RaphaŽl Troncy <Raphael.Troncy@cwi.nl>
Cc: Conrad Parker <conrad@metadecks.org>, 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>

I think we should be consistent and have the Range request also
contain the dimension, like so:

Range: <dimension>[':' <unit>] '=' <start time> - <end time>

Cheers,
Silvia.
Received on Saturday, 19 September 2009 05:57:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 September 2011 12:13:34 GMT