RFC 3236 (rfc3236) - Page 2 of 8

The 'application/xhtml+xml' Media Type

RFC 3236         The 'application/xhtml+xml' Media Type     January 2002


   This document follows the convention set out in [XMLMIME] for the
   MIME subtype name; attaching the suffix "+xml" to denote that the
   entity being described conforms to the XML syntax as defined in XML
   1.0 [XML].

   This document was prepared by members of the W3C HTML working group
   based on the structure, and some of the content, of RFC 2854, the
   registration of 'text/html'.  Please send comments to www-
   , a public mailing list (requiring subscription) with
   archives at .

2. Registration of MIME media type application/xhtml+xml

    MIME media type name:      application
    MIME subtype name:         xhtml+xml
    Required parameters:       none
    Optional parameters:

      charset
         This parameter has identical semantics to the charset parameter
         of the "application/xml" media type as specified in [XMLMIME].

      profile
         See Section 8 of this document.

   Encoding considerations:
      See Section 4 of this document.

   Security considerations:
      See Section 7 of this document.

   Interoperability considerations:
      XHTML 1.0 [XHTML10] specifies user agent conformance rules that
      dictate behaviour that must be followed when dealing with, among
      other things, unrecognized elements.

      With respect to XHTML Modularization [XHTMLMOD] and the existence
      of XHTML based languages (referred to as XHTML family members)
      that are not XHTML 1.0 conformant languages, it is possible that
      'application/xhtml+xml' may be used to describe some of these
      documents.  However, it should suffice for now for the purposes of
      interoperability that user agents accepting
      'application/xhtml+xml' content use the user agent conformance
      rules in [XHTML1].







Baker & Stark                Informational