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

2009/9/17 Raphaël Troncy <Raphael.Troncy@cwi.nl>:
> All,
>
> The minutes of today's F2F meeting are available for review at
> http://www.w3.org/2009/09/17-mediafrag-minutes.html
>
> Jack (and Yves), I encourage you to go through it and let us know if you
> have any concerns with the taken resolution.
>
> My quick summary is:
>  - RESOLUTION: we agree that aspect ratio is not a fragment and will not be
> something that we can address with a Media Fragment URI
>  - ACTION-109: Erik and Davy to write a paragraph in the document to explain
> why we don't include this feature in the spec (rationale) based on the group
> analysis
>
>  - We agree on the respective role of '#' and '?'. The border will be
> whether a transcoding process will be needed or not on server side to
> satisfy the request.
>  - ACTION-110: Silvia to draft a summary starting from her blog post and
> these IRC minutes in the document
>
>  - We agree on the syntax for expressing a Range request, using the HTTPBis
> clarification for having custom units and we are sure that this syntax will
> work for the temporal dimension. We will investigate if it works also for
> the other dimensions ...
>  - 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.

Conrad.

>
> ALL: please amend this if I have forgotten something. Talk to you tomorrow
> morning ...
> Cheers.
>
>  Erik & 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 09:54:23 UTC