Re: LINK TYPE=override/type

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


Message-Id: <199801231938.MAA00223@underworld.bigpic.com>
From: "Neil St.Laurent" <neil@bigpic.com>
To: Benjamin Franz <snowhare@netimages.com>
Date: Fri, 23 Jan 1998 12:45:49 -0600
CC: www-html@w3.org
Subject: Re: LINK TYPE=override/type

> I repeat: MISMATCHED 'TYPE' AND 'CONTENT-TYPE' IS AN ERROR.  There is no
> question of 'priority' here. The situation should never arise in the first
> place..

And since text/css is not a valid MIME type (brought up from before, 
I'm going on that) there is no possibility that a correct server can 
actually return a content type of text/css and thus no browser can 
actually ever link to a cascading style sheet.

Any future type has to then be first an accepted MIME type before it 
can be recognized by a browser.  This also requires that all site 
administrators cater to the needs of all of their users who have web 
pages with different types of files.
 
Ever since the computer industry began it has been natural to want to 
display documents with a type that differs from their standard type, 
thus the use of HEx utilities and other text viewers.  Consider even 
that an EXE can be viewed either as an executable and run or the 
header information of that file can be displayed.

It seems both inpractical and foolish to assume that the server knows 
what type of documents it stores and what mime type they correlate 
to.  In reference to the language attribute the server isn't given 
such credence, so why do we do this with document type?

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