- From: Norman Walsh <ndw@nwalsh.com>
- Date: Fri, 15 Oct 2004 15:45:37 -0400
- To: public-webarch-comments@w3.org
- Cc: Karl Dubost <karl@w3.org>
- Message-id: <87lle7ahpa.fsf@nwalsh.com>
/ Norman Walsh <ndw@nwalsh.com> was heard to say: | * 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. I don't find your use case compelling. It sounds like you're having trouble configuring your server to provide options for text/html or text/plain. Be seeing you, norm -- Norman Walsh <ndw@nwalsh.com> | Everything should be made as simple as http://nwalsh.com/ | possible, but no simpler.
Received on Friday, 15 October 2004 19:46:06 UTC