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

Re: ISSUE-2: What is the mime type of a media fragment? What is its relation with its parent resource?

From: RaphaŽl Troncy <Raphael.Troncy@cwi.nl>
Date: Tue, 27 Jan 2009 14:49:58 +0100
Message-ID: <497F1106.2040002@cwi.nl>
To: Michael Hausenblas <michael.hausenblas@deri.org>
CC: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Media Fragment <public-media-fragment@w3.org>

Hi Michael,

> Though I'm not Yves, my take on it is:

All opinions are more than welcome ...


>>From RFC2046 we learn that the MIME Type Registrations for JPEG 2000
> (ISO/IEC15444) is specified in RFC3745 [15] where no fragments are defined,
> hence the general rules from RFC3986 apply.
> My conclusion: in order to obey the rules of the game, we'd need to update
> all registries of targeted media types.

First, that is not possible, as we have already discussed it, since for 
updating IANA registries, you need to 'own' the format, which obviously 
we don't. It seems to me insane to try to register the fragment 
semantics for the 100+ multimedia formats, without counting all new ones 
appearing every year ...

Second, it is from my point of view not necessary. XPointer lives 
without for a period of time without problem. I cannot find a registry 
for the SVG fragment? Is someone aware of that?

Third, that was not really the question asked in the ISSUE, although, I 
agree it is not completely clear. The server specifies using http header 
what is the type of the resource is serving. Silvia's suggestion is to 
encode in the URI this type, for example, in the case we extract a 
keyframe from the video. Is it the only way to go?

Best regards.


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 Tuesday, 27 January 2009 13:50:44 UTC

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