Lists Home |
Date Index |
- From: David Brownell <firstname.lastname@example.org>
- To: Chris Lilley <email@example.com>
- Date: Sun, 04 Apr 1999 20:43:07 -0700
> > > > > What this RFC appears to do is remove author control over correctly
> > > > > labelling the encoding, and ensure that most if not all XML documents
> > > > > get incorrectly labelled as US-ASCII.
> > > >
> > > > Not at all. The best default MIME content type for all web
> > > > servers is "application/xml".
> > >
> > > Why? Do you consider anything not written in US-ASCII as a text
> > > document? I think the Unicode Consortium would disagree with you there.
> > No, and that's not what I said:
> But it is the implication of your argument.
How could it imply that? I didn't even talk about what "text" is,
only about what MIME guarantees. And MIME only talks about what some
specific content/media type categories mean, not about what "text" is.
(I certainly hope you see how those are different!)
See RFC 2046 and the discussion in section 4.1.2 for further information.
It says eight bit or multibyte encoded "text/*" "MUST" use a "charset=..."
property, which you seem to dislike; perhaps you were unaware that MIME
has fundamental constraints in this area. RFC 2376 is being compatible
with this fundamental Internet standard, which IMHO is the right idea.
> > For a single world-wide default; that's easily understood by overworked,
> > underpaid, often untrained sysadmins; and hence is NOT error prone (!!),
> > there's a simple answer that's guaranteed to work right everywhere that
> > pays more than lip service to industry standards, and hence is "best".
> > Namely, that servers report XML documents as "application/xml".
That requires _no conclusions_ about what is or is not "text".
It only says that encoded text is most likely to be dealt with in
the correct way if people label XML text as "application/xml".
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)