RFC 3023:XML Media Types
RFC-Ref

Entity


Click on the red underlined text to get to the source

... media types -- text/xml, application/xml, text/xml-external-parsed-entity, application/xml-external-parsed-entity ...
... entity, application/xml-external-parsed-entity, and application/xml-dtd -- as well as a naming convention for identifying XML-based ...
... for an XML MIME entity. For these reasons, the best approach for labeling XML network ...


... MIME and XML have defined the term entity, with different meanings. Section 2.4 of [RFC2045] says: ...
... "The term 'entity' refers specifically to the MIME-defined header fields and contents of either a message or one of the parts in the ...
... MIME-defined header fields and contents of either a message or one of the parts in the body of a multipart entity." ...
... In this document, "XML MIME entity" is defined as the latter (an XML entity ...
... entity" is defined as the latter (an XML entity) encapsulated in the former (a MIME entity ...
... entity) encapsulated in the former (a MIME entity). ...


... XML MIME entities: text/xml, application/xml, text/xml-external-parsed-entity, application/xml-external-parsed-entity ...
... entity, application/xml-external-parsed-entity, and application/xml-dtd. Registration information ...
... application/xml MAY be used for "document entities", while text/xml- external-parsed-entity or application/xml-external-parsed-entity ...
... external-parsed-entity or application/xml-external-parsed-entity SHOULD be used for "external parsed entities". The media type ...
... example, by displaying the XML MIME entity as plain text. Application/xml is preferable when the XML ...
... Application/xml is preferable when the XML MIME entity is unreadable by casual users. Similarly, text/xml-external-parsed-entity is ...
... MIME entity is unreadable by casual users. Similarly, text/xml-external-parsed-entity is preferable when an external parsed entity is readable by casual ...
... by casual users. Similarly, text/xml-external-parsed-entity is preferable when an external parsed entity is readable by casual users, but application/xml-external-parsed-entity ...
... entity is readable by casual users, but application/xml-external-parsed-entity is preferable when a plain text display is inappropriate. ...
... MIME-like mechanism). Thus, if an XML document or external parsed entity is encoded in such character encoding schemes, it cannot be labeled as text/xml or ...
... character encoding schemes, it cannot be labeled as text/xml or text/xml-external-parsed-entity (except for HTTP). ...
... registration in Section 3.2). The same rules apply to the distinction between text/xml-external- parsed-entity and application/xml-external-parsed-entity. ...
... parsed-entity and application/xml-external-parsed-entity. ...
... character encoding of the XML MIME entity. The charset parameter can also be used to provide protocol-specific ...
... If the XML MIME entity is transmitted via HTTP, which uses a MIME ...
... transform the XML MIME entity from text/xml; charset="utf-16" to application/xml ...
... Conformant with [RFC2046], if a text/xml entity is received with the charset parameter omitted, MIME ...
... where the XML MIME entity is transmitted via HTTP, the default charset ...
... provides persistent storage of the received XML MIME entity (e.g., in a file system). Unless the charset ...
... within the XML MIME entity. Encoding considerations ...
... the XML MIME entity. The charset parameter can also be used to provide protocol-specific ...
... If an application/xml entity is received where the charset parameter is omitted, no information is being provided about the charset ...
... the charset parameter is omitted from an application/xml entity. There are several reasons that the charset parameter ...
... provides persistent storage of the received XML MIME entity (e.g., in a file system). Unless the charset ...
... within the XML MIME entity. Encoding considerations ...
... Text/xml-external-parsed-entity Registration ...
... MIME subtype name: xml-external-parsed-entity Mandatory parameters ...
... The charset parameter of text/xml-external-parsed-entity is handled the same as that of text/xml as described in Section 3.1. ...
... Application/xml-external-parsed-entity Registration ...
... MIME subtype name: xml-external-parsed-entity Mandatory parameters ...
... The charset parameter of application/xml-external-parsed-entity is handled the same as that of application/xml as described in ...
... Interoperability considerations: Same as those for text/xml- external-parsed-entity as described in Section 3.3. Published specification: Same as text/xml as described in Section ...
... The following list applies to text/xml, text/xml-external-parsed- entity, and XML-based media types under the top-level type ...
... application/xml, application/xml-external- parsed-entity, application/xml-dtd, and XML-based media types ...


... charsets. When an XML MIME entity is encoded in "utf-16le" or "utf-16be", it MUST NOT begin with the BOM but SHOULD ...


... URI reference embedded in a MIME entity is dependent on the base URI. The base URI ...
... base URI is either (1) the base URI embedded in the MIME entity, (2) the base URI of the encapsulating MIME ...
... (2) the base URI of the encapsulating MIME entity, (3) the URI used to retrieve the MIME ...
... URI used to retrieve the MIME entity, or (4) the application-dependent default base URI, where (1) has the highest precedence. [RFC2396] further ...
... define such a mechanism for text/xml, application/xml, text/xml- external-parsed-entity, and application/xml-external-parsed-entity. ...
... external-parsed-entity, and application/xml-external-parsed-entity. The current specification for XML Base is available at ...


... XML generically to detect that the MIME entity is supposed to be an XML document, verify this assumption by invoking some XML processor ...
... media types defined in this document -- text/xml, application/xml, text/xml-external-parsed-entity, and application/xml-external-parsed-entity ...
... entity, and application/xml-external-parsed-entity -- also represent XML MIME entities while not conforming to the '*/*+xml' pattern.) ...
... charset of the XML MIME entity. ...


... the XML MIME entity. For UTF-16 examples, the Byte Order Mark ...
... to come at the beginning of the XML MIME entity, immediately following the BOM. Note that other MIME headers ...
... the XML MIME entity may contain other data in addition to the XML declaration; the examples focus on the Content-type header ...
... MIME and XML processors MUST treat the enclosed entity as UTF-8 encoded. ...
... XML MIME entity MUST use a content-transfer-encoding of either quoted- printable or base64 ...
... This is possible only when the XML MIME entity is transmitted via HTTP, which uses a MIME ...
... when the XML MIME entity is transmitted via HTTP. ...
... MIME and XML processors MUST treat the enclosed entity as encoded per RFC 1557. ...
... [RFC2046]. The default of "us-ascii" holds even if the text/xml entity is transported using HTTP. ...
... example, even if the contents of the XML MIME entity are UTF-16 or UTF-8 ...
... UTF-8, or the XML MIME entity has an explicit encoding declaration, XML ...
... MIME and XML processors MUST treat the enclosed entity as UTF-16 encoded. ...
... NNTP), the XML MIME entity MUST be encoded in quoted-printable or base64 ...
... provided, MIME and XML processors MUST treat the enclosed entity as UTF-16BE encoded. ...
... MIME and XML processors MUST treat the enclosed entity as encoded per RFC 1557, independent of whether the XML ...
... XML MIME entity has an internal encoding declaration (this example does show such a declaration, which agrees with the charset parameter ...
... UTF-16 XML MIME Entity ...
... For this example, the XML MIME entity begins with a BOM. Since the charset ...
... charset of the XML MIME entity. ...
... Application/xml with Omitted Charset and UTF-8 Entity ...
... UTF-8. The XML MIME entity does not contain an encoding declaration, but since the encoding ...
... this is still a conforming XML MIME entity. ...
... charset of the XML MIME entity. ...
... BOM. However, the XML MIME entity does have an encoding declaration inside the XML ...
... declaration inside the XML MIME entity that specifies the entity's charset ...
... XML MIME entity that specifies the entity's charset. Following the requirements ...
... XML MIME entity (in this example, UCS-4). ...
... charset of the XML MIME entity. ...
... Text/xml-external-parsed-entity with UTF-8 Charset ...
... Content-type: text/xml-external-parsed-entity; charset="utf-8" ...
... This is the recommended charset value for use with text/xml- external-parsed-entity. Since the charset parameter is provided, MIME ...
... MIME and XML processors MUST treat the enclosed entity as UTF-8 encoded. ...
... SMTP), the XML MIME entity MUST use a content-transfer-encoding of either quoted-printable ...
... Application/xml-external-parsed-entity with UTF-16 Charset ...
... Content-type: application/xml-external-parsed-entity; charset="utf-16" ...
... charset value for use with application/xml- external-parsed-entity. Since the charset parameter is provided, MIME ...
... MIME and XML processors MUST treat the enclosed entity as UTF-16 encoded. ...
... NNTP), the XML MIME entity MUST be encoded in quoted-printable or base64 ...
... Application/xml-external-parsed-entity with UTF-16BE Charset ...
... Content-type: application/xml-external-parsed-entity; charset="utf-16be" ...
... MIME and XML processors MUST treat the enclosed entity as UTF-16BE encoded. ...
... MIME and XML processors MUST treat the enclosed entity as UTF-8 encoded. ...
... MIME and XML processors MUST treat the enclosed entity as UTF-8 encoded. That is, the "iso-8859-1" encoding ...


... In general, any information stored outside of the direct control of the user -- including CSS style sheets, XSL transformations, entity declarations, and DTDs -- can be a source of insecurity, by either ...
... The entity lists and DTDs for XHTML 1.0[XHTML ...
... Apart from the structural possibilities, another option, "entity spoofing," can be used to insert text into documents, vandalizing and ...
... perhaps conveying an unintended message. Because XML 1.0 permits multiple entity declarations, and the first declaration takes precedence, it's possible to insert malicious content where an entity ...
... multiple entity declarations, and the first declaration takes precedence, it's possible to insert malicious content where an entity is used, such as by inserting the full text of Winnie the Pooh in every occurrence of —. ...
... XML documents that make use of what XML terms "entity references" (using the XML meaning of the term "entity ...
... entity references" (using the XML meaning of the term "entity" as described in Section 2), to construct repeated expansions of text. Recursive expansions are prohibited by [XML] and ...


... MIME type as part of the message structure and then decides whether to fetch the MIME entity. Requiring these fetches just to determine whether the MIME type is ...


... First, text/xml-external-parsed-entity and application/xml-external- parsed-entity ...
... entity and application/xml-external- parsed-entity are added as media types for external parsed entities, and text/xml and application/xml ...



Google
Web
RFC-Ref