- From: Dan Connolly <connolly@w3.org>
- Date: Thu, 02 Feb 2006 16:29:37 -0600
- To: Mark Baker <distobj@acm.org>
- Cc: www-tag@w3.org
On Fri, 2006-02-03 at 08:53 +1100, Mark Baker wrote: > Thanks for the clarifications, but ... > > On 2/3/06, Dan Connolly <connolly@w3.org> wrote: > > Well, there need only be one registered media type that works this > > way. > > How can that be? The TAG has already said[1] that new formats should > get new media types, right? True; meanwhile, issue uriMediaType-9 is still open... > How would this media type change that? The idea is to migrate from a central registry of media types to just using the web as a registry. So new formats would continue to get all the documentation that media types have always gotten, but they wouldn't need to get registered by anybody in particular, so long as they got a nice persistent URI with available representations. > Are you perhaps thinking that the URI in the parameter could be used > to dispatch applications? Yes. > If so, I don't think that's workable as > virtually all (AFAICT) software that dispatches off media types, does > it off the media type name independent of the value of any parameters. In such a dispatch slot, we insert a handler for t9 that dispatches further. Eventually, the dispatch API should evolve to just use URIs. Or... that's the idea, anyway. > [1] http://www.w3.org/2001/tag/2002/0129-mime (admittedly, this was > superceded by a finding[2] which doesn't say that, exactly) > [2] http://www.w3.org/2001/tag/2004/0430-mime > > Mark. -- Dan Connolly, W3C http://www.w3.org/People/Connolly/ D3C2 887B 0F92 6005 C541 0875 0F91 96DE 6E52 C29E
Received on Thursday, 2 February 2006 22:29:46 UTC