W3C home > Mailing lists > Public > public-media-fragment@w3.org > March 2009

Re: Linked Media: Weaving non-textual content into the semantic web

From: RaphaŽl Troncy <Raphael.Troncy@cwi.nl>
Date: Sun, 08 Mar 2009 23:13:04 +0100
Message-ID: <49B442F0.2090502@cwi.nl>
To: Michael Hausenblas <michael.hausenblas@deri.org>
CC: Philippe Le Hegaret <plh@w3.org>, Media Fragment <public-media-fragment@w3.org>
Dear Michael,

> Could you please detail out that one? Seems like an interesting question,
> but without further details hard to answer. What is a smart UA? What sort of
> clever processing? Which custom HTTP headers?

Sure, sorry, there was indeed a lot of implicit in these few lines. When 
designing the Media Fragment URI specification, the WG has already 
wondered how the old-fashioned and the new UA (e.g. a web browser) will 
react facing a Media Fragment URI.

A old-fashioned UA (e.g. a current web browser) will behave as 
currently: strip the hash and send the request to the server.
What I called a smart UA (e.g. the next release of your browser, or your 
current browser with an appropriate plugin) will strip the hash, but 
encode (part of) the fragment into custom http headers while sending the 
request to the server. This is what I called "clever processing".

The old-fashioned server might not understand these new headers, and 
will therefore send the whole resource to the UA, while the new media 
server will handle it and behave as we expect.

Regarding the "which custom HTTP headers" question: these are for 
example the ones described in the 2-way and 4-way handshakes. Actually, 
we imagine currently new unit(s) for the range http header, and possible 
a new http header.
Does that answer your question?


RaphaŽl Troncy
CWI (Centre for Mathematics and Computer Science),
Science Park 123, 1098 XG Amsterdam, The Netherlands
e-mail: raphael.troncy@cwi.nl & raphael.troncy@gmail.com
Tel: +31 (0)20 - 592 4093
Fax: +31 (0)20 - 592 4312
Web: http://www.cwi.nl/~troncy/
Received on Sunday, 8 March 2009 22:13:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:27:42 UTC