Lists Home |
Date Index |
- From: "Borden, Jonathan" <email@example.com>
- To: "'xml-dev'" <firstname.lastname@example.org>
- Date: Wed, 16 Dec 1998 22:17:56 -0500
At first glance it seems tempting to map MIME headers to XML as attributes.
This doesn't work well.
1) attributes don't obey order as elements do.
2) MIME headers can be duplicated (for example the Received: list in an
For these reasons, I map MIME headers to elements in XMTP.
The DTD is here:
Multiple transforms, some of which may include encryption etc, can be
represented as encapsulated MIME messages, the order of transformation of
which is required to be unambiguous.
If you would like to test this, I have placed a demo at:
JABR Technology Corp.
> There's always the option of creating a NOTATION which itself defines the
> particular processing pipeline, as in
> <!NOTATION midi-gzip-base64 SYSTEM "http://www.foo.com/midi/gzip/base64">
> where the information contained at the URL will tell you, in
> addition to the
> necessary info about each individual "notation", about the ordering of
> processing inorder to recover the source data.
> But I think this example shows the limitations of the "general" solution
> that NOTATIONS provide. Being general means that everyone has to
> the wheel in many cases on top of that generality.
> Paul V. Biron
> SGML Business Analyst
> Kaiser Permanente, So Cal.
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)