RFC 3023:XML Media Types
RFC-Ref

media type


Click on the red underlined text to get to the source

... XML network entities, this document standardizes five new media types -- text/xml, application/xml, text/xml-external-parsed-entity ...
... application/xml-dtd -- as well as a naming convention for identifying XML-based MIME media types. ...
... WebDAV[RFC2518] protocol for remote web authoring. Thus, there is a need for a media type to properly label the exchange of XML network ...
... SGML) ISO 8879[SGML], which has been assigned the media types text/sgml and application/sgml, there are several reasons why use of text/sgml or application/sgml to label XML ...
... labeling XML network entities is to provide new media types for XML. ...
... conventionally been assigned IETF tree media types, and since similar media types (HTML ...
... tree media types, and since similar media types (HTML, SGML) have been assigned IETF ...
... SGML) have been assigned IETF tree media types, the XML media types also belong in the IETF ...
... tree media types, the XML media types also belong in the IETF media types tree ...
... the XML media types also belong in the IETF media types tree. ...
... Similarly, XML will be used as a foundation for other media types, including types in every branch of the IETF media types ...
... media types, including types in every branch of the IETF media types tree. To facilitate the processing of such types, media types ...
... media types tree. To facilitate the processing of such types, media types based on XML, but that are not identified using text/xml or application/xml ...
... other processors -- to work with all XML-based media types. ...


... XML Media Types ...
... This document standardizes five media types related to XML MIME entities: text/xml, application/xml ...
... application/xml-dtd. Registration information for these media types is described in the sections below. ...
... entities", "external DTD subsets", "external parsed entities", and "external parameter entities". The media types text/xml and application/xml MAY be used for "document entities", while text/xml- ...
... application/xml-external-parsed-entity SHOULD be used for "external parsed entities". The media type application/xml-dtd SHOULD be used for "external DTD ...
... The top-level media type "text" has some restrictions on MIME entities and they are described in [RFC2045] and [RFC2046 ...
... XML provides a general framework for defining sequences of structured data. In some cases, it may be desirable to define new media types that use XML but define a specific application of XML ...
... domain-specific security considerations or runtime information. Furthermore, such media types may allow UTF-8 or UTF-16 only and ...
... UTF-16 only and prohibit other charsets. This document does not prohibit such media types and in fact expects them to proliferate. However, developers of such media types are STRONGLY RECOMMENDED to use this document as ...
... charsets. This document does not prohibit such media types and in fact expects them to proliferate. However, developers of such media types are STRONGLY RECOMMENDED to use this document as a basis for their registration. In particular, the charset parameter ...
... MIME media type name: text MIME subtype name ...
... of MIME bodies of the top-level media type "text" without reference to any of the internal content. Thus, it is possible that some agent ...
... Encoding considerations: This media type MAY be encoded as appropriate for the charset and the capabilities of the underlying ...
... XML]. Applications which use this media type: XML is device-, platform-, and vendor ...
... MIME media type name: application MIME subtype name ...
... Encoding considerations: This media type MAY be encoded as appropriate for the charset and the capabilities of the underlying ...
... Published specification: Same as Section 3.1. Applications which use this media type: Same as Section 3.1. Additional information: Same as Section 3.1. ...
... MIME media type name: text MIME subtype name ...
... Published specification: Same as Section 3.1. Applications which use this media type: Same as Section 3.1. Additional information: ...
... MIME media type name: application MIME subtype name ...
... 3.1. Applications which use this media type: Same as Section 3.1. Additional information: ...
... MIME media type name: application MIME subtype name ...
... 3.1. Applications which use this media type: DTD authoring tools handle ...
... entity, and XML-based media types under the top-level type "text" that define the charset parameter ...
... entity, application/xml-dtd, and XML-based media types under top-level types other than "text" that define the charset parameter ...


... resulting from a retrieval action, and that the format and interpretation of fragment identifiers is dependent on the media type of the retrieval result. ...
... As of today, no established specifications define identifiers for XML media types. However, a working draft published by W3C, namely "XML ...


... specifies that the mechanism for embedding the base URI is dependent on the media type. ...


... A Naming Convention for XML-Based Media Types ...
... suffix of '+xml') for identifying XML-based MIME media types, whatever their particular content may represent. This allows the use of generic XML processors and technologies on a wide variety of different XML document ...
... XML processors and technologies on a wide variety of different XML document types at a minimum cost, using existing frameworks for media type registration. ...
... rapidly. Many of these XML document types would benefit from the identification possibilities of a more specific MIME media type than text/xml or application/xml can provide, and it is likely that many ...
... text/xml or application/xml can provide, and it is likely that many new media types for XML-based document types will be registered in the near and ongoing future. ...
... When a new media type is introduced for an XML-based format, the name of the media type ...
... media type is introduced for an XML-based format, the name of the media type SHOULD end with '+xml'. This convention will allow applications that can process XML generically to detect that the MIME ...
... MIME entities by comparing the subtype to the pattern '*/*+xml'. (Of course, 4 of the 5 media types defined in this document -- text/xml, application/xml, text/xml-external-parsed-entity ...
... XML generic processing is not always appropriate for XML-based media types. For example, authors of some such media types may wish that the types remain entirely opaque ...
... XML generic processing is not always appropriate for XML-based media types. For example, authors of some such media types may wish that the types remain entirely opaque except to applications that are ...
... the types remain entirely opaque except to applications that are specifically designed to deal with that media type. By NOT following the naming convention '+xml', such media types can avoid XML ...
... specifically designed to deal with that media type. By NOT following the naming convention '+xml', such media types can avoid XML-generic processing. Since generic processing will be useful in many cases, ...
... processing. Since generic processing will be useful in many cases, however -- including in some situations that are difficult to predict ahead of time -- those registering media types SHOULD use the '+xml' convention unless they have a particularly compelling reason not to. ...
... The registration process for these media types is described in [RFC2048]. The registrar for the IETF ...
... tree will encourage new XML- based media type registrations in the IETF tree to follow this ...
... Registrations for new XML-based media types under the top-level type "text" SHOULD, in specifying the charset parameter ...
... Registrations for new XML-based media types under top-level types other than "text" SHOULD, in specifying the charset parameter ...
... These registrations SHOULD specify that the XML-based media type being registered has all of the security considerations described in ...
... security considerations described in RFC 3023prop plus any additional considerations specific to that media type. ...
... 3023prop in specifying interoperability considerations, if these considerations are not overridden by issues specific to that media type. ...


... RFC2781], the UTF-16 family MUST NOT be used with media types under the top-level type "text" except over HTTP ...
... charset is "us- ascii", the default charset value for text media types specified in [RFC2046]. The default of "us-ascii" holds even if the text/xml ...
... identifier. However, no content type has yet been registered for MathML and so this media type should not be used until such registration has been completed. ...
... content type has yet been registered for XSLT and so this media type should not be used until such registration has been completed. ...
... content type has yet been registered for RDF and so this media type should not be used until such registration has been completed. ...
... identifier. However, no content type has yet been registered for SVG and so this media type should not be used until such registration has been completed. ...


... Levinson, E., "SGML Media Types", RFC 1874exp, December 1995. ...
... Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046draft, November 1996. ...
... Whitehead, E. and M. Murata, "XML Media Types", RFC 2376(-> 3023prop), July 1998. ...


... XML-based format such as image/svg+xml fits the definition of a MIME media type exactly as well as image/png[PNG ...
... processors that are also XML processors, XML-based media types -- even when treated as opaque, non-XML media types ...
... media types -- even when treated as opaque, non-XML media types -- are just as useful as any other media type and should be treated as such. ...
... opaque, non-XML media types -- are just as useful as any other media type and should be treated as such. ...
... MIME type, use of text/xml or application/xml to label discrete media types will hinder correct dispatching and general interoperability. Finally, many XML documents ...
... The subtree under which a media type is registered -- IETF, vendor ...
... (*/vnd.*), or personal (*/prs.*); see [RFC2048] for details -- is completely orthogonal from whether the media type uses XML syntax or not. The suffix ...
... create a new top-level MIME type for XML-based media types? ...
... image/* to signal acceptance of any image format should certainly be given access to media type image/svg+xml, which is in all respects a standard image ...
... image subtype. It just happens to use XML to describe its syntax. The two aspects of the media type are completely orthogonal. ...
... Rather than explicitly labeling XML-based media types, the processor could look inside each type and see whether or not it is XML ...
... processor could also cache a list of XML-based media types. ...
... A.5 Why not use a MIME parameter to specify that a media type uses XML syntax? ...
... media subtype, and as such do not fundamentally affect the nature of the content". However, all XML-based media types are by their nature always XML. Parameters, as they have been defined in the MIME ...
... architecture, are never invariant across all instantiations of a media type. ...
... XML processing, it has been suggested that it is easier to implement this functionality when acting off of the media type rather than a parameter. More important, sending agents require no update ...
... content type (e.g., an ecommerce engine for application/iotp+xml[RFC2801], once this media type is registered). ...
... content type, the top-level for the kind of content and the second-level for the specific media type. [RFC2048] extends this in an interoperable way by using prefixes ...
... semantics be assigned to its presence. Therefore, application/foo and application/foo+xml SHOULD be treated as completely independent media types. Although, for example, text/calendar+xml could be an XML version of text/calendar ...
... text/calendar[RFC2445], it is possible that this (hypothetical) new media type would include new semantics as well as new syntax, and in any case, there would be many applications that ...
... A.15 Why must I use the '+xml' suffix for my new XML-based media type? ...
... Whether the inventors of a media type, today, design it for dispatch to generic XML processing machinery (and most won't) is not the ...
... critical issue. The core notion is that the knowledge that some media type happens to use XML syntax opens the door to unanticipated kinds of processing beyond those envisioned by its inventors, and on ...
... Developers of new media types are often tightly focused on a particular type of processing that meets current needs. But there is no need to rule out generic processing as well, which could make your ...
... particular type of processing that meets current needs. But there is no need to rule out generic processing as well, which could make your media type more valuable over time. It is believed that registering with the '+xml' suffix will cause no interoperability ...


... application/xml-external- parsed-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 subsets and external parameter entities, and text/xml and ...
... Fourth, a naming convention ('+xml') for XML-based media types has been added, which also updates [RFC2048] as described in Section 7. ...
... RFC2048] as described in Section 7. By following this convention, an XML-based media type can be easily recognized as such. ...



Google
Web
RFC-Ref