I believe that we have agreed to introduce media types for XML DTDs
(to be precise, external DTD subsets and external parameter entities),
since they do not parse as XML documents.
I tried to sketch required changes to the current RFC. Here I introduced
both text/xml-dtd and application/xml-dtd. One could certainly argue
aginst this choice. Comments are greatly appreciated.
1) Revision to "3. XML Media types"
This document introduces four new media types for XML entities,
text/xml, application/xml, text/xml-dtd, and application/xml-dtd.
...
The media types text/xml and application/xml can be used for
"document entities" or "external parsed entities". For backward
compatibility, they can also be used for "external DTD subsets" or
"external parameter entities". The media types text/xml-dtd and
application/xml-dtd can be used for "external DTD subsetes" or
"external parameter entities".
2) Addition of two subsections for text/xml-dtd and application/xml-dtd
3.3 Text/xml-dtd Registration
MIME media type name: text
MIME subtype name: xml-dtd
Mandatory parameters: none
Optional parameters: charset
The charset parameter of text/xml-dtd is handled exactly
the same as that of text/xml.
Encoding considerations:
This media type may be encoded exactly the same as text/xml.
Security considerations:
See section 4 below.
Interoperability considerations:
XML DTDs has proven to be interoperable by DTD authoring
tools and XML WWW browsers among others.
Published specification: see [REC-XML]
Applications which use this media type:
DTD authoring tools handle external DTD subsets as well as external
parameter entities. XML browsers may also access external DTD subests
and external parameter entities.
Additional information:
Magic number(s): none
Although no byte sequences can be counted on to always be present,
external DTD subsets and external parameter entities in
ASCII-compatible charsets
(including UTF-8) often
begin with hexadecimal 3C 3F 78 6D 6C ("<?xml"). For more
information, see Appendix F of [REC-XML].
File extension(s): .dtd
Macintosh File Type Code(s): "TEXT"
Person & email address for further information:
Dan Connolly <connolly(_at_)w3(_dot_)org>
Murata Makoto (Family Given)
<murata(_at_)fxis(_dot_)fujixerox(_dot_)co(_dot_)jp>
Intended usage: COMMON
Author/Change controller:
The XML specification is a work product of the World Wide Web
Consortium's XML Working Group, and was edited by:
Tim Bray <tbray(_at_)textuality(_dot_)com>
Jean Paoli <jeanpa(_at_)microsoft(_dot_)com>
C. M. Sperberg-McQueen <cmsmcq(_at_)uic(_dot_)edu>
The W3C, and the W3C XML working group, has change control over
the XML specification.
3.4 Application/xml-dtd Registration
MIME media type name: application
MIME subtype name: xml-dtd
Mandatory parameters: none
Optional parameters: charset
The charset parameter of text/xml-dtd is handled exactly
the same as that of text/xml.
Encoding considerations:
The charset parameter of application/xml-dtd is handled exactly
the same as that of application/xml.
Security considerations:
See section 4 below.
Interoperability considerations:
XML DTDs has proven to be interoperable by DTD authoring
tools and XML WWW browsers among others.
Published specification: see [REC-XML]
Applications which use this media type:
DTD authoring tools handle external DTD subsets as well as external
parameter entities. XML browsers may also access external DTD subests
and external parameter entities.
Additional information:
Magic number(s): none
Although no byte sequences can be counted on to always be present,
external DTD subsets and external parameter entities in
ASCII-compatible charsets
(including UTF-8) often
document entities and external parsed entities in ASCII-compatible
charsets
(including UTF-8) often
begin with hexadecimal 3C 3F 78 6D 6C ("<?xml"), and those in
UTF-16 often begin with hexadecimal FE FF 00 3C 00 3F 00 78 00 6D
or FF FE 3C 00 3F 00 78 00 6D 00 (the Byte Order Mark (BOM)
followed by "<?xml"). For more information, see Annex F of [REC-
XML].
File extension(s): .dtd
Macintosh File Type Code(s): "TEXT"
Person & email address for further information:
Dan Connolly <connolly(_at_)w3(_dot_)org>
Murata Makoto (Family Given)
<murata(_at_)fxis(_dot_)fujixerox(_dot_)co(_dot_)jp>
Intended usage: COMMON
Author/Change controller:
The XML specification is a work product of the World Wide Web
Consortium's XML Working Group, and was edited by:
Tim Bray <tbray(_at_)textuality(_dot_)com>
Jean Paoli <jeanpa(_at_)microsoft(_dot_)com>
C. M. Sperberg-McQueen <cmsmcq(_at_)uic(_dot_)edu>
The W3C, and the W3C XML working group, has change control over
the XML specification.
3) Addition of examples in sectino 6
6.10 text/xml-dtd with UTF-8 Charset
Content-type: text/xml-dtd; charset="utf-8"
<?xml version="1.0" encoding="utf-8"?>
This is the recommended charset value for use with text/xml-dtd. Since
the charset parameter is provided, MIME and XML processors must treat
the enclosed entity as UTF-8 encoded.
6.11 application/xml-dtd with UTF-16 Charset
Content-type: application/xml-dtd; charset="utf-16"
{BOM}<?xml version="1.0"?>
This is a recommended charset value for use with application/xml-dtd.
Since the charset parameter is provided, MIME and XML processors must
treat the enclosed entity as UTF-16 encoded.
Cheers,
Makoto
Fuji Xerox Information Systems
Tel: +81-44-812-7230 Fax: +81-44-812-7231
E-mail: murata(_at_)apsdc(_dot_)ksp(_dot_)fujixerox(_dot_)co(_dot_)jp