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: Conrad Parker <conrad@metadecks.org>
Date: Sat, 19 Sep 2009 16:00:51 +0900
Message-ID: <dba6c0830909190000gca51693hbd70ceabb6a23c23@mail.gmail.com>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Cc: RaphaŽl Troncy <Raphael.Troncy@cwi.nl>, Media Fragment <public-media-fragment@w3.org>, Jack Jansen <Jack.Jansen@cwi.nl>, Yves Lafon <ylafon@w3.org>
2009/9/19 Silvia Pfeiffer <silviapfeiffer1@gmail.com>:
> 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>

+1

Conrad.
Received on Saturday, 19 September 2009 07:07:07 GMT

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