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

[Jonathan Borden]

John Cowan wrote:

>Jonathan Borden wrote:
>
>>         Please explain what:
>>
>> Content-type: text/xhtml
>>
>>         can possibly do for you that:
>>
>> Content-type: text/xml; doctype="http://www.w3.org/xhtml.dtd"
>>
>>         cannot do. (Note: the use of doctype = dtd is an example, the
doctype can
>> point to any URI. Just like the XML namespace URI, the doctype URI serves
as
>> a unique identifier and implies no particular meaning.
>
>I agree, except that I would prefer to see an FPI rather than (or
>in addition to) a URI.  That would be extensible to HTML as well as
>XHTML, and therefore to the text/html media type as well as the
>text/xml media type.
>

This is a good idea.

A general way to employ the Content-type header to specify a document type
is:

Content-type: text/xml; element="html"; fpi="-//W3C//DTD XTHML 1.0
Strict//EN";              uri="http://www.w3.org/XHTML.DTD"

This should apply to text/html, text/xml, text/sgml, application/xml etc.

deja vu all over again :-)

Jonathan Borden
http://jabr.ne.mediaone.net




xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)