If no explicit MIME type exists for a specific XML format, text/xml shall be used. Consumers
who read a value of text/xml should determine the contents by the root namespace of the
contents of the part.
[21]
Bug 155730 – Mozilla doesn't handle files served as */*+xml as XML files (2007-02-10 14:34:20 +09:00 版) https://bugzilla.mozilla.org/show_bug.cgi?id=155730
[36] draft-murata-kohn-lilley-xml-03 - XML Media Types
( 版)
http://tools.ietf.org/html/draft-murata-kohn-lilley-xml
[37] Web Applications 1.0 r6661 Make the */*+xml handling be fallback handling, rather than overriding any registered handlers for specific XML types.
( ( 版))
http://html5.org/tools/web-apps-tracker?from=6660&to=6661
[38] W3C XML Schema Definition Language (XSD) 1.1 Part 1: Structures
( ( 版))
http://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/#web-representation
[47] Index of /2006/02/son-of-3023
( 版)
http://www.w3.org/2006/02/son-of-3023/
[85] Re: [apps-discuss] Last Call: <draft-ietf-appsawg-xml-mediatypes-09.txt> (XML Media Types) to Proposed Standard
( (Paul Grosso 著, 版))
http://lists.w3.org/Archives/Public/public-xml-core-wg/2014Mar/0003.html
[107] OASIS Open Document Format for Office Applications (OpenDocument) Version 1.2 - Part 1: OpenDocument Schema
( ( 版))
http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#__RefHeading__1420348_2538929491
[10] OASIS Open Document Format for Office Applications (OpenDocument) Version 1.2 - Part 1: OpenDocument Schema
( 版)
http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#__RefHeading__1420348_2538929491
Office documents that conform to this specification but are not contained in a package should use the MIME type text/xml.
[13] 155730 – (*/*+xml) Mozilla doesn't handle files served as */*+xml as XML files
( 版)
https://bugzilla.mozilla.org/show_bug.cgi?id=155730
[14] RFC 6546 - Transport of Real-time Inter-network Defense (RID) Messages over HTTP/TLS
( 版)
https://tools.ietf.org/html/rfc6546
As RID documents are XML,
the RID media type is 'text/xml'; i.e., the 'Content-type' Request
and Response headers MUST be 'text/xml'.
[18] XProc 2.0: An XML Pipeline Language
()
https://www.w3.org/TR/2016/NOTE-xproc20-20160721/#introduction
The media type for pipeline documents is application/xml. Often, pipeline documents are identified by the extension .xpl.
[19] Let [MIMESNIFF] define MIME-related concepts
(domenic著, )
https://github.com/whatwg/html/commit/0d08aea0733e5ad21f15f626b64d413a8c447083
[20] XPath and XQuery Functions and Operators 3.1
()
https://www.w3.org/TR/2017/REC-xpath-functions-31-20170321/#func-unparsed-text
if the media type of the resource is text/xml or application/xml (see [RFC 2376]), or if it matches the conventions text/*+xml or application/*+xml (see [RFC 7303] and/or its successors), then the encoding is recognized as specified in [Extensible Markup Language (XML) 1.0 (Fifth Edition)]
[115] RFC 5689 - Extended MKCOL for Web Distributed Authoring and Versioning (WebDAV)
()
https://tools.ietf.org/html/rfc5689#section-3
The Content-Type
request header MUST be set appropriately for an XML body (e.g., set
to "text/xml" or "application/xml").
[116] Editorial: use HTML/XML MIME type terms
(annevk著, )
https://github.com/whatwg/xhr/commit/daa0baea431703640e1d35fde8db8cd5050f578b
[118] Editorial: use HTML/XML MIME type terms by annevk · Pull Request #171 · whatwg/xhr
()
https://github.com/whatwg/xhr/pull/171
[119] Define a new MIME type model, parser, and serializer
(annevk著, )
https://github.com/whatwg/mimesniff/commit/cc81ec48288944562c4554069da1d74a71e199fb
[120] Multimodal Architecture and Interfaces
()
https://www.w3.org/TR/2012/REC-mmi-arch-20121025/
The Content-Type header field of the HTTP/POST request has to be set according to the lifecycle event format, e.g. “text/xml”.
[121] CORB: protecting certain nosniff and 206 responses
(anforowicz著, )
https://github.com/whatwg/fetch/commit/794dd5452705564538440cc5b2c1f13d909e2f9a