RFC 3023:XML Media Types
RFC-Ref

application/xml


Click on the red underlined text to get to the source

... network entities, this document standardizes five new media types -- text/xml, application/xml, text/xml-external-parsed-entity, application/xml ...
... application/xml, text/xml-external-parsed-entity, application/xml-external-parsed-entity, and application/xml-dtd -- as ...
... application/xml-external-parsed-entity, and application/xml-dtd -- as well as a naming convention for identifying XML-based MIME media types ...
... media types based on XML, but that are not identified using text/xml or application/xml, SHOULD be named using a suffix of '+xml' as described in Section 7. This ...


... media types related to XML MIME entities: text/xml, application/xml, text/xml-external-parsed-entity, application/xml ...
... application/xml, text/xml-external-parsed-entity, application/xml-external-parsed-entity, and application/xml-dtd. ...
... application/xml-external-parsed-entity, and application/xml-dtd. Registration information for these media types ...
... "external parameter entities". The media types text/xml and application/xml MAY be used for "document entities", while text/xml- external-parsed-entity or application/xml ...
... application/xml MAY be used for "document entities", while text/xml- external-parsed-entity or application/xml-external-parsed-entity SHOULD be used for "external parsed entities". The media type ...
... SHOULD be used for "external parsed entities". The media type application/xml-dtd SHOULD be used for "external DTD subsets" or "external parameter entities". application/xml ...
... application/xml-dtd SHOULD be used for "external DTD subsets" or "external parameter entities". application/xml and text/xml MUST NOT be used for "external parameter entities" or "external DTD subsets", ...
... XML document -- is readable by casual users, text/xml is preferable to application/xml. MIME user agents (and web user agents ...
... MIME entity as plain text. Application/xml is preferable when the XML MIME entity ...
... preferable when an external parsed entity is readable by casual users, but application/xml-external-parsed-entity is preferable when a plain text display is inappropriate. ...
... Text/xml and application/xml behave differently when the charset parameter is not explicitly specified. If the default charset (i.e., ...
... US-ASCII) for text/xml is inconvenient for some reason (e.g., bad web servers), application/xml provides an alternative (see "Optional parameters" of application/xml registration ...
... web servers), application/xml provides an alternative (see "Optional parameters" of application/xml registration in Section 3.2). The same rules apply to the distinction between text/xml-external- ...
... same rules apply to the distinction between text/xml-external- parsed-entity and application/xml-external-parsed-entity. ...
... An XML document labeled as text/xml or application/xml might contain namespace declarations, stylesheet-linking processing instructions ...
... entity from text/xml; charset="utf-16" to application/xml; charset="utf-16". ...
... Application/xml Registration ...
... XML]. If an application/xml entity is received where the charset parameter is omitted, no information is being provided about the ...
... charset if the charset parameter is omitted from an application/xml entity. ...
... Application/xml-external-parsed-entity Registration ...
... The charset parameter of application/xml-external-parsed-entity is handled the same as that of application/xml ...
... application/xml-external-parsed-entity is handled the same as that of application/xml as described in Section 3.2. ...
... Application/xml-dtd Registration ...
... The charset parameter of application/xml-dtd is handled the same as that of application/xml as described in Section 3.2. ...
... charset parameter of application/xml-dtd is handled the same as that of application/xml as described in Section 3.2. Encoding considerations ...
... The next list applies to application/xml, application/xml-external- parsed-entity ...
... The next list applies to application/xml, application/xml-external- parsed-entity, application/xml ...
... application/xml-external- parsed-entity, application/xml-dtd, and XML-based media types under ...


... Language (XPointer)", attempts to define fragment identifiers for text/xml and application/xml. The current specification for XPointer is available at http://www.w3.org/TR/xptr. ...


... W3C, namely "XML Base", attempts to define such a mechanism for text/xml, application/xml, text/xml- external-parsed-entity, and application/xml ...
... application/xml, text/xml- external-parsed-entity, and application/xml-external-parsed-entity. The current specification for XML ...


... identification possibilities of a more specific MIME media type than text/xml or application/xml can provide, and it is likely that many new media types for XML-based document ...
... course, 4 of the 5 media types defined in this document -- text/xml, application/xml, text/xml-external-parsed-entity, and application/xml ...
... application/xml, text/xml-external-parsed-entity, and application/xml-external-parsed-entity -- also represent XML MIME entities ...
... charset parameter / encoding considerations] of application/xml as specified in RFC 3023prop." ...


... Application/xml with UTF-16 Charset ...
... Content-type: application/xml; charset="utf-16" ...
... This is a recommended charset value for use with application/xml. Since the charset parameter is provided, MIME ...
... Application/xml with UTF-16BE Charset ...
... Content-type: application/xml; charset="utf-16be" ...
... Application/xml with ISO-2022-KR Charset ...
... Content-type: application/xml; charset="iso-2022-kr" ...
... This example shows application/xml with a Korean charset (e.g., Hangul) encoded following the specification in [RFC1557 ...
... Application/xml with Omitted Charset and UTF-16 XML ...
... Content-type: application/xml {BOM ...
... Application/xml with Omitted Charset and UTF-8 Entity ...
... Content-type: application/xml <?xml version ...
... Application/xml with Omitted Charset and Internal Encoding ...
... Content-type: application/xml <?xml version ...
... Application/xml-external-parsed-entity with UTF-16 Charset ...
... Content-type: application/xml-external-parsed-entity; charset ...
... This is a recommended charset value for use with application/xml- external-parsed-entity. Since the charset parameter ...
... Application/xml-external-parsed-entity with UTF-16BE Charset ...
... Content-type: application/xml-external-parsed-entity; charset ...
... Application/xml-dtd ...
... Content-type: application/xml-dtd; charset="utf-8" ...
... Charset "utf-8" is a recommended charset value for use with application/xml-dtd. Since the charset parameter is provided, MIME ...


... A.1 Why not just use text/xml or application/xml and let the XML processor dispatch to the correct application based on the referenced DTD ...
... text/xml and application/xml remain useful in many situations, especially for document-oriented applications that involve combining XML ...
... MIME dispatchers work off of the MIME type, use of text/xml or application/xml to label discrete media types will hinder correct dispatching and general interoperability ...
... A.6 How about labeling with parameters in the other direction (e.g., application/xml; Content-Feature=iotp)? ...


... First, text/xml-external-parsed-entity and application/xml-external- parsed-entity are added as media types ...
... entity are added as media types for external parsed entities, and text/xml and application/xml are now prohibited. ...
... Second, application/xml-dtd is added as a media type for external DTD ...
... DTD subsets and external parameter entities, and text/xml and application/xml are now prohibited. ...



Google
Web
RFC-Ref