Lists Home |
Date Index |
- From: "Jonathan Borden" <email@example.com>
- To: "David Megginson" <firstname.lastname@example.org>, "xml mailing list" <email@example.com>
- Date: Wed, 24 Feb 1999 19:59:14 -0500
David Megginson wrote:
> Isn't it easier to identify the resource type externally so
> that it can be handed directly to the correct processor?
Assuming that HTML is defined in XML, then isn't the correct processor the
XML processor? text/xml correctly identifies the content-type. If you make
an exception for the specific XHTML DTD then why not for every DTD! The
argument that text/xhtml for content negotiation is a shaky one because the
problem of content negotiation is a well known problem for HTTP. Proposed
solutions include RFC 2295. A better solution is to employ specific
request/response headers e.g.
Content-Type: text/xml; document-type=http://www.w3.org/html50.dtd;
The problem with content-type proliferation is that lots of software depends
on known content-types. For example, how can you programmatically tell if a
MIME message body contains XML? Parse it and if it succeeds then TRUE?
Its alot easier to add a new header recognized by new UAs than it is to
modify legacy and currently working code.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)