Skip to main content

XML Media Types
draft-lilley-xml-mediatypes-00

Document Type Replaced Internet-Draft (candidate for appsawg WG)
Expired & archived
Authors Chris Lilley , Murata Makoto , Alexey Melnikov , Henry S. Thompson
Last updated 2012-11-27 (Latest revision 2012-10-15)
Replaces draft-murata-kohn-lilley-xml
Replaced by draft-ietf-appsawg-xml-mediatypes
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-appsawg-xml-mediatypes
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

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 a convention (using the suffix '+xml') for naming media types outside of these five types when those media types represent XML MIME 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 [RFC3023] are alignment of charset handling for text/xml and text/xml-external-parsed-entity with application/ xml, the addition of XPointer and XML Base as fragment identifiers and base URIs, respectively, mention of the XPointer Registry, and updating of many references.

Authors

Chris Lilley
Murata Makoto
Alexey Melnikov
Henry S. Thompson

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)