RFC 7303: XML Media Types
In plain English — editorial summary, not part of the RFC
This specification standardizes three media types -- application/xml, application/xml-external-parsed-entity, and application/xml-dtd -- for use in exchanging network entities that are related to the Extensible Markup Language (XML) while defining text/xml and text/ xml-external-parsed-entity as aliases for the respective application/ types. This specification also standardizes the '+xml' suffix for naming media types outside of these five types when those media types represent XML MIME entities.
Document record
- Document ID
- RFC7303
- Published
- July 2014
- Authors
- H. Thompson; C. Lilley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 35
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2376 (1998)
- RFC 3023 (2001)
- RFC 7303 (2014)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7310RTP Payload Format for Standard apt-X and Enhanced apt-X CodecsCurrent
July 2014
- RFC 7294RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Concealment Metrics Reporting on Audio ApplicationsCurrent
July 2014
- RFC 7293The Require-Recipient-Valid-Since Header Field and SMTP Service ExtensionCurrent
July 2014
- RFC 7320URI Design and OwnershipObsoleted
July 2014
- RFC 7332Loop Detection Mechanisms for Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUAs)Current
August 2014
- RFC 7266RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Mean Opinion Score (MOS) Metric ReportingCurrent
June 2014
- RFC 7340Secure Telephone Identity Problem Statement and RequirementsCurrent
September 2014
- RFC 7264An Extension to the REsource LOcation And Discovery (RELOAD) Protocol to Support Relay Peer RoutingCurrent
June 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?