Re: LINK TYPE=override/type

Neil St.Laurent (neil@bigpic.com)
Fri, 23 Jan 1998 12:56:52 -0600


Message-Id: <199801231949.MAA00230@underworld.bigpic.com>
From: "Neil St.Laurent" <neil@bigpic.com>
To: igraham@smaug.java.utoronto.ca (Ian Graham)
Date: Fri, 23 Jan 1998 12:56:52 -0600
CC: www-html@w3.org
Subject: Re: LINK TYPE=override/type

> an HTTP/server forum, since it would not be hard to adapt servers to allow
> better control, by users, of the HTTP-defined types of their resources..
> I argue for fixing HTTP server administration, as opposed to using HTML
> to 'patch over' the problem..

One should propose that the MIME Type be used as a file extension and 
thus avoid this potentially dangerous mapping concept.  Consider

index.text_html (slash replaced to avoid directory concerns)

<LINK rel=stylesheet href="style.text_css">

In this example both the server and the browser will have the exact 
same impression of the file type, and thus removing the need for the 
TYPE attribute.

Basically if the Content Type is so fundamental to the document then 
it should be fully associated with that document somehow, and a 
character string name seems most appropriate since servers can't 
necessarily do the correct mapping.

Now, how to indicate the character set...


__  __  __  __  __  __  __  __  __  __  __  __  __  __  __  __  __
 Mortar: Advanced Web Development      <http://mortar.bigpic.com/>
 Neil St.Laurent                     <mailto:stlaurent@bigpic.com>
 Big Picture Multimedia                            +1.403.265.8018