Media Fragments spec and HTTP

It's been pointed out to me that the W3C Media Fragments URI 1.0 specification is in Second Last Call, and contains some new HTTP-related values, including:

* a variety of new range specifiers:

* new HTTP header "Content-Range-Mapping":

* new HTTP headers "Accept-Range-Redirect" and "Range-Redirect":

I may have missed others; I've only had a quick look,and it's a big document.

One thing that jumped out at me was examples like this:

  Range: t:npt=10-20;include-setup

... even though "t:npt" is not identified as a range unit (only "t" is).

Is anyone willing to have a look at this from an HTTP perspective? I note Yves is listed as a contributor, but it would be good to have a bit more cross-review.


Mark Nottingham

Received on Thursday, 12 May 2011 06:25:51 UTC