RE: text/xhtml+xml vs. application/xhtml+xml
Dan Kohn <dan@dankohn.com> Wed, 01 November 2000 19:17 UTC
Received: by ns.secondary.com (8.9.3/8.9.3) id LAA05569 for ietf-xml-mime-bks; Wed, 1 Nov 2000 11:17:49 -0800 (PST)
Received: from mgate-02.teledesic.com (mgate-02.teledesic.com [216.190.22.44]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id LAA05564 for <ietf-xml-mime@imc.org>; Wed, 1 Nov 2000 11:17:47 -0800 (PST)
Received: from mgate-02.teledesic.com (localhost [127.0.0.1]) by mgate-02.teledesic.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id WC14HSQ8; Wed, 1 Nov 2000 11:24:08 -0800
Received: from 10.100.10.13 by mgate-02.teledesic.com (InterScan E-Mail VirusWall NT); Wed, 01 Nov 2000 11:24:08 -0800 (Pacific Standard Time)
Received: from mgate-01.teledesic.com ([10.100.10.14]) by 10.100.10.13 (Norton AntiVirus for Internet Email Gateways 1.0) ; Wed, 01 Nov 2000 19:24:08 0000 (GMT)
Received: by MGATE-01 with Internet Mail Service (5.5.2650.21) id <WC1TTWRL>; Wed, 1 Nov 2000 11:24:06 -0800
Message-ID: <25D0C66E6D25D311B2AC0008C7913EE00105A2F9@tdmail2.teledesic.com>
From: Dan Kohn <dan@dankohn.com>
To: Gavin Thomas Nicol <gtn@ebt.com>, ietf-xml-mime@imc.org
Subject: RE: text/xhtml+xml vs. application/xhtml+xml
Date: Wed, 01 Nov 2000 11:24:05 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>
Gavin, I just want to point out that no one is arguing that MHTML is a bad thing. It's just that in retrospect, we wish application/html had been used. But, just because we are locked into text/html, does not mean that we need to repeat the same mistakes for new media types. For a description of the evolving view of where text types are (and are not) appropriate, see Section 3.3 of RFC 2646 <http://www.normos.org/ietf/rfc/rfc2646.txt> and Section 3 of <http://www.imc.org/draft-murata-xml>. (For a description of when to do +xml, see Section 7 of the latter.) Further, it has been stated that it is better to have a single registration rather than registering under both text and application, since if we are having trouble evaluating the tradeoffs, it seems unlikely that most document authors would understand the subtlety. I subscribe to section 3.2 of RFC 1958 on Architectural Principles of the Internet, which says, "If there are several ways of doing the same thing, choose one." >From my understanding, everyone else on this list agrees with this direction, and sees a certain consistency there. Rather than doing a line by line rebuttal of certain points, could I suggest that you state an alternative viewpoint for future registrations (such as "always do text unless the material is binary"), and then we can compare that viewpoint to the ones listed above. Otherwise, the discussion becomes needlessly abstract. - dan -- Dan Kohn <mailto:dan@dankohn.com> <http://www.dankohn.com> <tel:+1-650-327-2600> -----Original Message----- From: Gavin Thomas Nicol [mailto:gtn@ebt.com] Sent: Wednesday, 2000-11-01 09:59 To: ietf-xml-mime@imc.org Subject: RE: text/xhtml+xml vs. application/xhtml+xml > This continued argument about the exact nature of past > mistakes is going nowhere fast, so I'm not going to > bother to respond further to it. Fine. One question though... Given 1) choices for types text/xml application/xml application/foo+xml 2) clear guidelines on their use. do *you* have faith that developers will do what is right?
- RE: text/xhtml+xml vs. application/xhtml+xml ned.freed
- Re: text/xhtml+xml vs. application/xhtml+xml John Cowan
- Re: text/xhtml+xml vs. application/xhtml+xml John Cowan
- RE: text/xhtml+xml vs. application/xhtml+xml Gavin Thomas Nicol
- RE: text/xhtml+xml vs. application/xhtml+xml Gavin Thomas Nicol
- Re: text/xhtml+xml vs. application/xhtml+xml John Cowan
- RE: text/xhtml+xml vs. application/xhtml+xml ned.freed
- RE: text/xhtml+xml vs. application/xhtml+xml Gavin Thomas Nicol
- RE: text/xhtml+xml vs. application/xhtml+xml Gavin Thomas Nicol
- RE: text/xhtml+xml vs. application/xhtml+xml ned.freed
- RE: text/xhtml+xml vs. application/xhtml+xml ned.freed
- RE: text/xhtml+xml vs. application/xhtml+xml Gavin Thomas Nicol
- RE: text/xhtml+xml vs. application/xhtml+xml Gavin Thomas Nicol
- RE: text/xhtml+xml vs. application/xhtml+xml Dan Kohn
- RE: text/xhtml+xml vs. application/xhtml+xml Gavin Thomas Nicol
- Re: text/xhtml+xml vs. application/xhtml+xml Mark Baker
- Re: XHTML vs HTML media types Mark Baker
- Re: text/xhtml+xml vs. application/xhtml+xml Martin J. Duerst
- RE: XHTML vs HTML media types ned.freed
- Re: text/xhtml+xml vs. application/xhtml+xml ned.freed
- Re: text/xhtml+xml vs. application/xhtml+xml Keith Moore
- RE: XHTML vs HTML media types Larry Masinter
- RE: text/xhtml+xml vs. application/xhtml+xml Dan Kohn
- Re: text/xhtml+xml vs. application/xhtml+xml Simon St.Laurent
- XHTML vs HTML media types Mark Baker
- Re: text/xhtml+xml vs. application/xhtml+xml Mark Baker
- text/xhtml+xml vs. application/xhtml+xml Dan Kohn
- Re: text/xhtml+xml vs. application/xhtml+xml Mark Baker
- Re: text/xhtml+xml vs. application/xhtml+xml Keith Moore
- Re: text/xhtml+xml vs. application/xhtml+xml Dave Peterson
- Re: text/xhtml+xml vs. application/xhtml+xml Rick Jelliffe
- Re: text/xhtml+xml vs. application/xhtml+xml John Cowan
- RE: text/xhtml+xml vs. application/xhtml+xml Rick Jelliffe
- RE: text/xhtml+xml vs. application/xhtml+xml Simon St.Laurent
- RE: text/xhtml+xml vs. application/xhtml+xml Gavin Thomas Nicol
- RE: text/xhtml+xml vs. application/xhtml+xml Rick Jelliffe
- RE: text/xhtml+xml vs. application/xhtml+xml Dan Kohn
- RE: text/xhtml+xml vs. application/xhtml+xml Dan Kohn
- RE: text/xhtml+xml vs. application/xhtml+xml Rick Jelliffe
- RE: text/xhtml+xml vs. application/xhtml+xml ned.freed
- RE: text/xhtml+xml vs. application/xhtml+xml Simon St.Laurent
- RE: text/xhtml+xml vs. application/xhtml+xml Gavin Thomas Nicol
- RE: text/xhtml+xml vs. application/xhtml+xml ned.freed
- RE: text/xhtml+xml vs. application/xhtml+xml Gavin Thomas Nicol