…cs to the charset parameter of the "application/xml" media type as specified in RFC3023 ]. Encoding considerations: Identical to those of "application/xml" as described in [RFC3023], Section 3.2 Gregorio & de hOra Standards Track [Page 39] RFC 5023 The Atom Publishing Protocol Oc…

…cs to the charset parameter of the "application/xml" media type as specified in RFC3023 ]. Encoding considerations: Identical to those of "application/xml" as described in [RFC3023], Section 3.2 Gregorio & de hOra Standards Track [Page 39] RFC 5023 The Atom Publishing Protocol Oc…

…tional parameters Same as charset parameter of application/xml as specified in [RFC3023] Encoding considerations The encoding considerations of application/xml as specified in [RFC3023] apply. Security considerations As with other XML types and as noted in [RFC3023] section 10, r…

…al [Page 2] RFC 6839 Additional Media Type Suffixes January 2013 . Introduction RFC3023 ] created the +xml suffix convention that can be used when defining names for media types whose representation uses XML underneath. That is, they could have been successfully parsed as if the …

…f atom:content is a MIME media type [ MIMEREG ], but is not an XML media type [ RFC3023 ], does not begin with "text/", and does not end with "/xml" or "+xml". o atom:entry elements MUST NOT contain more than one atom:summary element. o atom:entry elements MUST contain exactly on…

…essors -- to work with all XML-based media types. This specification replaces [ RFC3023 ]. Major differences are in the areas of alignment of text/xml and text/xml-external-parsed-entity with application/xml and application/xml-external-parsed-entity respectively, the addition of…

… J. Boyer. This document is at http://www.w3.org/TR/xforms/#serialize-urlencode RFC3023 XML Media Types , M. Murata, S. St.Laurent, D. Kohn. RFC January 2001. This document is at http://www.ietf.org/rfc/rfc3023.txt RFC3986 Uniform Resource Identifier (URI): Generic Syntax , T. Be…

…e of atom:content is a MIME media type [MIMEREG], but is not an XML media type [RFC3023], does not begin with "text/", and does not end with "/xml" or "+xml". o atom:entry elements MUST NOT contain more than one atom:summary element. o atom:entry elements MUST contain exactly one…

… of atom:content is a MIME media type MIMEREG ], but is not an XML media type [ RFC3023 ], does not begin with "text/", and does not end with "/xml" or "+xml". o atom:entry elements MUST NOT contain more than one atom:summary element. o atom:entry elements MUST contain exactly on…

… of atom:content is a MIME media type MIMEREG ], but is not an XML media type [ RFC3023 ], does not begin with "text/", and does not end with "/xml" or "+xml". o atom:entry elements MUST NOT contain more than one atom:summary element. o atom:entry elements MUST contain exactly on…

… of atom:content is a MIME media type MIMEREG ], but is not an XML media type [ RFC3023 ], does not begin with "text/", and does not end with "/xml" or "+xml". o atom:entry elements MUST NOT contain more than one atom:summary element. o atom:entry elements MUST contain exactly on…

…s to the charset parameter of the "application/xml" media type as specified in [RFC3023] , section 3.2. Encoding considerations: Identical to those of "application/xml" as specified in [RFC3023] section 3.2. Security considerations: SPARQL query results uses URIs. See Section 7 o…

…rameters: none Optional parameters: charset as defined for application/xml in [ RFC3023 ]; per [ RFC3023 ], use of the charset parameter with the value "utf-8" is "STRONGLY RECOMMENDED". Encoding considerations: Same as encoding considerations of application/xml as specified in […

….1 . Encoding considerations: The same as the considerations in section 3.1 of [RFC3023] . Security considerations: See section 5 . Interoperability considerations: None, except as noted in other sections of this document. Published specification: [ JS15 ] Applications which use …

…rameters: none Optional parameters: charset as defined for application/xml in [ RFC3023 ]; per [ RFC3023 ], use of the charset parameter with the value "utf-8" is "STRONGLY RECOMMENDED". Encoding considerations: Same as encoding considerations of application/xml as specified in […