W3C home > Mailing lists > Public > public-media-fragment@w3.org > June 2010

Re: WWW/2008/WebVideo/Fragments/WD-media-fragments-spec overview.xml,1.92,1.93

From: Yves Lafon <ylafon@w3.org>
Date: Wed, 16 Jun 2010 04:23:26 -0400 (EDT)
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
cc: Media Fragment <public-media-fragment@w3.org>
Message-ID: <alpine.DEB.1.10.1006160423130.1417@wnl.j3.bet>
On Wed, 16 Jun 2010, Silvia Pfeiffer wrote:

> Hi Yves,
>
> I'm just looking through all the commits that were made yesterday. I
> think we have just dropped a particular application through this
> commit below, in particular this change:

Indeed, just fixed.

>
>
>> -Content-Range-Mapping      = "Content-Range-Mapping" ":" ( content-range-mapping-spec
>> -                             [ ";" "include-setup"] ) | "include-setup"
>> +Content-Range-Mapping      = "Content-Range-Mapping" ":" '{' content-range-mapping-spec
>> +                             [ ";" "include-setup"] '}' '=' '{'
>> +                             byte-content-range-mapping-spec '}'
>
>
> It needs to be possible to only reply with the setup information in a
> CRM header, because e.g. if you ask for a range that doesn't exist and
> you have an include-setup in the range, then the server has to reply
> with the setup alone. Therefore, we need to be able to return e.g.:
>
> Content-Range-Mapping : include-setup = bytes 0-45678
>
> This was why I had the CRM defined as it was before - I don't think
> that's possible any more. I think we need to change the production
> rule to:
>
> Content-Range-Mapping      = "Content-Range-Mapping" ":" '{'
> content-range-mapping-spec [ ";" "include-setup"] | "include-setup"
> '}' '=' '{' byte-content-range-mapping-spec '}'
>
>
> Cheers,
> Silvia.
>
>
> On Wed, Jun 16, 2010 at 12:35 AM, Yves Lafon via cvs-syncmail
> <cvsmail@w3.org> wrote:
>> Update of /w3ccvs/WWW/2008/WebVideo/Fragments/WD-media-fragments-spec
>> In directory hutz:/tmp/cvs-serv21922
>>
>> Modified Files:
>>        overview.xml
>> Log Message:
>> added byte range equivalence, matching
>> RESOLUTION: new syntax for the Content-Range-Mapping header, "Content-Range-Mapping: {t:npt 10-20/0-38;include-setup}={bytes 0-2000,4000-1000/2000}"
>>
>>
>> Index: overview.xml
>> ===================================================================
>> RCS file: /w3ccvs/WWW/2008/WebVideo/Fragments/WD-media-fragments-spec/overview.xml,v
>> retrieving revision 1.92
>> retrieving revision 1.93
>> diff -u -d -r1.92 -r1.93
>> --- overview.xml        15 Jun 2010 14:25:17 -0000      1.92
>> +++ overview.xml        15 Jun 2010 14:35:38 -0000      1.93
>> @@ -2359,8 +2359,14 @@
>>  ;
>>  ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; HTTP Response Headers ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>>  ;
>> -Content-Range-Mapping      = "Content-Range-Mapping" ":" ( content-range-mapping-spec
>> -                             [ ";" "include-setup"] ) | "include-setup"
>> +Content-Range-Mapping      = "Content-Range-Mapping" ":" '{' content-range-mapping-spec
>> +                             [ ";" "include-setup"] '}' '=' '{'
>> +                             byte-content-range-mapping-spec '}'
>> +
>> +byte-range-mapping-spec    = bytes-unit SP
>> +                             byte-range-resp-spec *( "," byte-range-resp-spec ) "/"
>> +                             ( instance-length / "*" )
>> +
>>  content-range-mapping-spec = time-mapping-spec | track-mapping-spec | name-mapping-spec
>>  time-mapping-spec          = timeprefix ":" time-mapping-options
>>  time-mapping-options       = npt-mapping-option / smpte-mapping-option / clock-mapping-option
>>
>>
>>
>
>

-- 
Baroula que barouleras, au tiéu toujou t'entourneras.

         ~~Yves
Received on Wednesday, 16 June 2010 08:23:28 GMT

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