- From: Yves Lafon <ylafon@w3.org>
- Date: Tue, 10 Mar 2009 11:07:10 -0400 (EDT)
- To: Raphaël Troncy <Raphael.Troncy@cwi.nl>
- cc: Conrad Parker <conrad@metadecks.org>, Media Fragment <public-media-fragment@w3.org>
On Tue, 10 Mar 2009, Raphaël Troncy wrote:
> Dear Conrad,
>
>> The distinction between use of a fragment or a query introduces
>> different retrieval protocols. This is a technical distinction and has
>> little to do with semantic purpose such as user context.
>
> Well, not exactly. The query creates a *new* resource that is unrelated to
> the original resource, i.e., you can't tell that
> http://www.example.org/myVideo.ogg?t=15,45 is unrelated to
> http://www.example.org/myVideo.ogg. You don't have this problem with the
> fragment.
Plus, consider that a server returning the same content for both URIs
above is a configuration choice, quite common now but perhaps not some
time in the future (like when a security warning say that you have to
reject every URI with query parameters on resources not handling them ;) )
So you can't even rely on a fallback mechanism to do discovery based on
the structure of the URI.
--
Baroula que barouleras, au tiéu toujou t'entourneras.
~~Yves
Received on Tuesday, 10 March 2009 15:07:20 UTC