suffix
Click on the red underlined text to get to the source
... 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
will allow XML-based tools ...
...
This document recommends the use of a naming convention (a suffix of
'+xml') for identifying XML-based MIME media types ...
... interoperability
problems or lack of future extensibility. The alternatives to the '
+xml' suffix and the reason for its selection are described in
Appendix A.
...
... mathematical information, as defined by [MathML]. As a format based
on XML, MathML documents SHOULD use the '+xml' suffix convention in
their MIME content-type identifier ...
... based on XML, XSLT documents SHOULD
use the '+xml' suffix convention in their MIME content-type
identifier ...
... RDF]. As a format based
on XML, RDF documents SHOULD use the '+xml' suffix convention in
their MIME content-type identifier ...
... SVG]. As a
format based on XML, SVG documents SHOULD use the '+xml' suffix
convention in their MIME content-type identifier ...
... interoperability
problems or lack of future extensibility. The alternatives to the
'+xml' suffix and the reason for its selection are described below.
...
... media type uses XML syntax or
not. The suffix approach allows XML document types to be identified
within any subtree ...
... include a large number of XML-based document types. By using a
suffix, rather than setting up a separate subtree, those types may
...
... registrations.
This specification also extends the two-level type by using the '
+xml' suffix. In both cases, processors that are unaware of these
later specifications treat them as opaque ...
... A.12 Why use the plus ('+') character for the suffix '+xml'? ...
... MIME processors that are unaware of XML will treat the '+xml' suffix
as completely opaque, so it is essential that no extra semantics ...
... later defined, and these documents were also XML, they would need to
specify that the '+xml' suffix is always the outermost suffix (e.g.,
application/foo+ebml+xml not application/foo+xml+ebml). If they were
...
... XML, they would need to
specify that the '+xml' suffix is always the outermost suffix (e.g.,
application/foo+ebml+xml not application/foo+xml+ebml). If they were
not XML ...
... application/foo+ebml+xml not application/foo+xml+ebml). If they were
not XML, then they would use a regular suffix (e.g.,
application/foo+ebml).
...
... You don't have to, but unless you have a good reason to explicitly
disallow generic XML processing, you should use the suffix so as not
to curtail the options of future users and developers.
...
... media type more valuable over time. It is believed that registering
with the '+xml' suffix will cause no interoperability problems
whatsoever, while it may enable significant new functionality and
...
... interoperability now and in the future. So, the conservative
approach is to include the '+xml' suffix.
...