- From: Norman Walsh <ndw@nwalsh.com>
- Date: Fri, 15 Oct 2004 15:24:45 -0400
- To: public-webarch-comments@w3.org
- Cc: Karl Dubost <karl@w3.org>
- Message-id: <87hdovdbsy.fsf@nwalsh.com>
* KD 016
5.1. Orthogonal Specifications
"""the software developer community would benefit from being able to
find all HTTP headers from the HTTP specification (including any
associated extension registries and specification updates per IETF
process). Perhaps as a result, this feature of the HTML specification
is not widely deployed. """
Not true. Use case. I'm a technical writer, I'm explaining how to
create an HTML file, foo.html, I give a link to the html representation
of foo.html and therefore served as text/html. Now I want to explain
the source code, and I would like to use the benefits of the object
element to display the source code of the same file. So I set in my
object element the text/plain mime type.
Though because of precedences rules of HTTP over HTML, the only way to
do is to not specify on the server side the mime type but only in the
meta of the HTML file. So that once it can be displayed as an HTML file
or it can be displayed as a text file.
In fact right now, the only possibility to do it without problems is to
create
foo.html and foo.html.txt
which is quite stupid.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Impatient people always arrive too
http://nwalsh.com/ | late.--Jean Dutourd
Received on Friday, 15 October 2004 19:25:07 UTC