W3C home > Mailing lists > Public > public-media-fragment@w3.org > May 2011

Re: minutes of 2011-05-11 teleconference

From: Davy Van Deursen <davy.vandeursen@ugent.be>
Date: Wed, 18 May 2011 08:39:56 +0200
Message-ID: <4DD369BC.6050100@ugent.be>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
CC: Media Fragment <public-media-fragment@w3.org>, RaphaŽl Troncy <raphael.troncy@eurecom.fr>
Silvia,

On 18/05/2011 3:18, Silvia Pfeiffer wrote:
> Nice work!
>
> I've spotted some remaining occurrences of "id":
> section 5.2.3:
>    Accept-Ranges: bytes, t, track, id
>
> section 6.2.1
>    (i.e., t, xywh, track, and id)
Thanks for catching these, I will correct them.

> Further on a note that Davy put into 4.2.3 Track Dimension:
> "We can also reference the HTML5 Media Multitrack API here, when it's
> mentioned in the HTML5 spec. "
> ->  yes, we absolutely should
> Do you want me to formulate an example?
Yes, please do!

> Finally about section 5.2.3 Server triggered redirect:
> can I suggest that instead of dropping it we re-set the example to use
> "chapters", because that would explain exactly how they are done?
Do you mean something like:

GET /video.ogv HTTP/1.1
Host: www.example.com
Accept: video/*
Range: chapter=chapter1

results in

HTTP/1.1 307 Temporary Redirect
Location: http://www.example.com/video.ogv#t=10,20
Accept-Ranges: bytes, t, chapter
Content-Length: 0
Content-Type: video/ogg
Link: <http://www.example.com/video.ogv#chapter=chapter1>;rel="fragment"
Vary: *

? (Also, I'm not sure 'fragment' is in this case the right relationship 
naming for the Link header ...)

Best regards,

Davy

-- 
Davy Van Deursen

Ghent University - IBBT
Department of Electronics and Information Systems - Multimedia Lab
URL: http://multimedialab.elis.ugent.be/dvdeurse
Received on Wednesday, 18 May 2011 06:40:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:46 UTC