XML Media Types (RFC3023)
Original Publication Date: 2001-Jan-01
Included in the Prior Art Database: 2019-Feb-14
Publishing Venue
Internet Society Requests For Comment (RFCs)
Related People
M. Murata: AUTHOR [+2]
Related Documents
Abstract
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. [STANDARDS-TRACK]
Network Working Group M. Murata Request for Comments: 3023 IBM Tokyo Research Laboratory Obsoletes: 2376 S. St.Laurent Updates: 2048 simonstl.com Category: Standards Track D. Kohn Skymoon Ventures January 2001
XML Media Types
Status of this Memo
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.
Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract
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".
Murata, et al. Standards Track [Page 1]
RFC 3023 XML Media Types January 2001
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Notational Conventions . . . . . . . . . . . . . . . . . . . 4 3. XML Media Types . . . . . . . . . . . . . . . . . . . . . . 5 3.1 Text/xml Registration . . . . . . . . . . . . . . . . . . . 7 3.2 Application/xml Registration . . . . . . . . . . . . . . . . 9 3.3 Text/xml-external-parsed-entity Registration . . . . . . . . 11 3.4 Application/xml-external-parsed-entity Registration . . . . 12 3.5 Application/xml-dtd Registration . . . . . . . . . . . . . . 13 3.6 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . 14 4. The Byte Order Mark (BOM) and Conversions to/from the UTF-16 Charset . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5. Fragment Identifiers . . . . . . . . . . . . . . . . . . . . 15 6. The Base URI . . . . . . . . . . . . . . . . . . . . . . . . 15 7. A Naming Convention for XML-Based Media Types . . . . . . . 16 7.1 Referencing . . . . . . . . . . . . . . . . . . . . . . . . 18 8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8.1 Text/xml with UTF-8 Charset . . . . . . . . . . . . . . . . 19 8.2 Text/xml with UTF-16 Charset . . . . . . . . . . . . . . . . 19 8.3 Text/xml with UTF-16...
