FW: RFC 3023 on XML Media Types
"Dan Kohn" <dan@dankohn.com> Thu, 18 January 2001 09:35 UTC
Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id BAA16812 for ietf-xml-mime-bks; Thu, 18 Jan 2001 01:35:37 -0800 (PST)
Received: from dfw-smtpout4.email.verio.net (dfw-smtpout4.email.verio.net [129.250.36.44]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id BAA16808 for <ietf-xml-mime@imc.org>; Thu, 18 Jan 2001 01:35:36 -0800 (PST)
Received: from [129.250.38.61] (helo=dfw-mmp1.email.verio.net) by dfw-smtpout4.email.verio.net with esmtp id 14JBZB-0000ml-00; Thu, 18 Jan 2001 09:41:13 +0000
Received: from [64.160.55.118] (helo=DAN3480) by dfw-mmp1.email.verio.net with asmtp (110190536) id 14JBZB-0001CN-00; Thu, 18 Jan 2001 09:41:13 +0000
From: Dan Kohn <dan@dankohn.com>
To: ietf-xml-mime@imc.org
Subject: FW: RFC 3023 on XML Media Types
Date: Thu, 18 Jan 2001 01:40:00 -0800
Message-ID: <BKEEIHEKOEPPHEPACHCOKECACCAA.dan@dankohn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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>
Publication day has finally arrived. Thanks everyone for their diligent efforts and comments. - dan -- Dan Kohn <mailto:dan@dankohn.com> <http://www.dankohn.com> <tel:+1-650-327-2600> -----Original Message----- From: RFC Editor [mailto:rfc-ed@ISI.EDU] Sent: Wednesday, 2001-01-17 15:36 To: IETF-Announce:; IETF-Announce:; @loki.ietf.org Cc: rfc-ed@ISI.EDU Subject: RFC 3023 on XML Media Types A new Request for Comments is now available in online RFC libraries. RFC 3023 Title: XML Media Types Author(s): M. Murata, S. St.Laurent, D. Kohn Status: Standards Track Date: January 2001 Mailbox: mmurata@trl.ibm.co.jp, simonstl@simonstl.com, dan@dankohn.com Pages: 39 Characters: 86011 Updates: 2376 I-D Tag: draft-murata-xml-09.txt URL: ftp://ftp.isi.edu/in-notes/rfc3023.txt This document standardizes five new media types -- text/xml, application/xml, text/xml-external-parsed-entity, application/xml-external-parsed-entity, and application/xml-dtd -- for use in exchanging network entities that are related to the Extensible Markup Language (XML). This document also standardizes a convention (using the suffix '+xml') for naming media types outside of these five types when those media types represent XML MIME (Multipurpose Internet Mail Extensions) entities. XML MIME entities are currently exchanged via the HyperText Transfer Protocol on the World Wide Web, are an integral part of the WebDAV protocol for remote web authoring, and are expected to have utility in many domains. Major differences from RFC 2376 are (1) the addition of text/xml-external-parsed-entity, application/xml-external-parsed-entity, and application/xml-dtd, (2) the '+xml' suffix convention (which also updates the RFC 2048 registration process), and (3) the discussion of "utf-16le" and "utf-16be". This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- FW: RFC 3023 on XML Media Types Dan Kohn