Binary Data in XML

Jonathan A. Borden jborden at
Wed Sep 30 20:31:05 BST 1998

ricko wrote:
> One approach for naming would be to use the HTTP/MIME
> header names, where we can.  A PCDATA element type with
> some encoded data reveals that there is a class of NDATA entities
> which may be too small or frequent in a document to warrant being
> stored as external resources.  So it is logical that much of the HTTP/MIME
> header information may also be relevent and useful to these "inlined
> NDATA entities".
> I am not suggesting that all the HTTP/MIME headers need to be duplicated
> now; certainly if Tim makes his note, it should be modest. But I
> think it probable that over time more HTTP/MIME headers will
> be found to be appropriate to add as attributes in this kind of element.
Actually, there's no reason not to develop a complete and interoperable
mapping between MIME and XML. This would create an XML native transport
protocol (XMTP? or SXTP? hmmm :-). People with validating parsers could turn
off acceptance of undefined MIME types etc. e.g. "application/x-whatever".

What do people think this mapping should look like. Based upon some of the
work we are doing, we have a need for this and will probably develop a
mapping ourselves unless there is an interest from others in specifying

Jonathan Borden
mailto:jborden at

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as:
To (un)subscribe, mailto:majordomo at the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list