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

ACTION-194: "Add an intro paragraph in the section 5 to explain which recipes is useful for which dimension"

From: RaphaŽl Troncy <raphael.troncy@eurecom.fr>
Date: Wed, 01 Dec 2010 10:33:02 +0100
Message-ID: <4CF6164E.9020506@eurecom.fr>
To: Media Fragment <public-media-fragment@w3.org>
Dear all,

In response to ACTION-194, I have added this paragraph:

"This section defines the different exchange scenarios for the 
situations explained in the section 3 URI fragment and URI query over 
the HTTP protocol. Various recipes are proposed depending on the 
dimension addressed in the media fragment URI, the container and codec 
formats used by the media resource, or some advanced processing features 
implemented by the User Agent. Hence, if the container format of the 
media resource is fully indexable (e.g. MP4, OGG or WebM) and if the 
time dimension is requested in the media fragment URI, the User Agent 
MAY priviledge the recipe described in the section 5.1 Protocol for URI 
fragment Resolution in HTTP since it will be in a position of issuing 
directly a normal RANGE request expressed in terms of byte ranges. On 
the other hand, if the container format of the media resource is a 
legacy format such as AVI, the Use Agent MAY priviledge the recipe 
described in the section 5.1.2 Server mapped byte ranges, issuing a 
RANGE request expressed with a custom unit such as seconds and waiting 
for the server to provide the mapping in terms of byte ranges. Finally, 
if the track dimension is requested in the media fragment URI, the User 
Agent MAY priviledge the recipe described in the section 5.1.3 Server 
triggered redirect."

Tracker, this is ACTION-194.

   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.eurecom.fr/~troncy/
Received on Wednesday, 1 December 2010 09:36:35 GMT

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