Re: LINK TYPE=override/type

Neil St.Laurent (neil@bigpic.com)
Thu, 22 Jan 1998 11:16:32 -0600


Message-Id: <199801221808.LAA00450@underworld.bigpic.com>
From: "Neil St.Laurent" <neil@bigpic.com>
To: Bill Bereza <bereza@pobox.com>
Date: Thu, 22 Jan 1998 11:16:32 -0600
CC: www-html@w3.org
Subject: Re: LINK TYPE=override/type

> I'd have to disagree with this suggestion. In the case of conflicting
> TYPE value and MIME type (from HTTP) I think that the specified TYPE
> value should have precedence. I think of TYPE as being used like 
> type casting in some programming language, where it can be used to
> over-ride or change the actual type of the resource. I can imagine that
> there are many times when an authour would like to or have to over-ride
> the server-specified type. 

I'm again going to say that this behaviour seems both plausible, 
implementable, and reasonible.  I see no reason why we should have to 
rely on the server being setup correctly in order for the files to 
work the way we intend them to.

This would save the browser lots of effort in cases such as:

<LINK REL=STYLESHEET HREF="s.css" TYPE="text/css">
<LINK REL=STYLESHEET HREF="s.dsssl" TYPE="text/dsssl">

The Browser can quickly determine which resource to use, of course if 
it supports both that is another story...
 
__  __  __  __  __  __  __  __  __  __  __  __  __  __  __  __  __
 Mortar: Advanced Web Development      <http://mortar.bigpic.com/>
 Neil St.Laurent                     <mailto:stlaurent@bigpic.com>
 Big Picture Multimedia                            +1.403.265.8018