RE: Range syntax

> -----Original Message-----
> From: Raphaël Troncy [mailto:Raphael.Troncy@cwi.nl]
> Sent: vendredi 11 septembre 2009 10:59
> To: DENOUAL Franck
> Cc: public-media-fragment@w3.org
> Subject: Re: Range syntax
> 
> Hi Frank,
> 
> > Content-Range: xywh 160,120,320,240/4:00:00
> > Content-Range: xywh:pixel 160,120,320,240/4:00
> > Content-Range: xywh:percent 25,25,50,50/4:00
> >
> > I think that for Content-Range, it would be more coherent to have the
> > same unit between the range and the instance length:
> >
> > ie: Content-Range: <spatialarea> ' ' <topleftx> ',' <toplefty>','
> > <width>',' <height>
> >                 '/' <total width>','<total_heigth>
> 
> Very good question! That's why I think Yves just work out the temporal
> dimension so far :-) So what should be the instance-length when using
> the spatial, track and name dimensions?

For spatial I maintain: instance-length = <total_width>','<total_height>
For track and name, one could 
1- use the escape (asterisk) character: 
Content-Range: track 'video'/*' (means that instance-length is unknown at the time when the response was generated.)
2- use default unit for the current access type (one unit per access type (track/id/combination/...) to define)
Content-Range: track 'video'/4:00:00 (with default unit being npt time) 
3- provide the unit to consider for instance-length :
Content-Range: track:npt 'video'/4:00:00
Content-Range: track:pixel 'video'/352,240
This is not really elegant since the unit (npt/pixel) would apply only on the instance-length, not on the range (since none actually but ID instead).

--
	Franck.

> 
>    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, 11 September 2009 12:19:17 UTC