W3C home > Mailing lists > Public > www-html-editor@w3.org > January to March 1999

Re: Content-Document-Type: was (Re: MIME types vs. DOCTYPE)

From: Walter Underwood <wunder@infoseek.com>
Date: Fri, 26 Feb 1999 09:42:26 -0800
Message-Id: <3.0.5.32.19990226094226.03c98770@corp>
To: xml-dev@ic.ac.uk
Cc: www-html-editor@w3.org
I feel that Content-document-type is a poor idea. It put something
specific to XML in a generic header.

Not all clients care about the doctype. Some (like search engines)
don't need to render it. Others may just need to cache it.

If a document is XHTML, and should have a default rendering, I'd
call that a processing instruction:

  <?xhtml version="1.0" doctypes="strict, frameset">

or whatever does the job.

The objection about thin clients or palmtops not wanting to download
large files doesn't really hold water. XML will generally be the 
smallest files. Mine are almost always smaller than the corresponding
HTML. Powerpoint, PDF, JPEG -- those are big files. 

Adding an XML-specific HTTP header line makes HTTP 1.1 more complex
(shudder), and imposes an extra coding and testing burden on HTTP
implementations. Also, it does nothing for XHTML over other transports,
like SMTP or FTP.

Essentially, this is document information, not protocol information. 
It belongs in the document. To describe the document out-of-line, 
use RDF, not HTTP headers.

Pragmatically, HTTP Content-type isn't even reliable. Somebody will 
decide that Excel and XML are the same thing, and start serving 
spreadsheets as text/xml. Cell phones have to deal with that world, 
and adding things to the HTTP spec doesn't fix ignorant sysadmins. 
And lots of web servers serve application-specific files (MS Word,
Powerpoint, Excel) as application/octet-stream in order to force 
the browser to put up a save box rather than display them in the 
frame. We see this sort of stuff all the time with the search engine.

XHTML Spec comment: the spec doesn't mention application/xml. It should. 
If application/xml is never appropriate for XHTML (say, the UTF-16
encoding is forbidden), then say so.

XHTML Spec comment: Are the Strict, Transitional, and Frameset DTDs
subsets or extensions? Or neither? Is one a subset of another? These
intentions should be spelled out in the spec so that future versions
won't break them.

wunder

--
Walter R. Underwood
wunder@infoseek.com
wunder@best.com (home)
http://software.infoseek.com/cce/ (my product)
http://www.best.com/~wunder/
1-408-543-6946
Received on Friday, 26 February 1999 12:51:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:16:44 GMT