Paul Hoffman / IMC <phoffman(_at_)imc(_dot_)org> writes:
I propose to leave the type application/iotp and to drop this discussion
until there is a request for a real-world application where thre would be
some advantage to the end user for application/foo-xml to be handed to an
XML viewer directly instead of being written to disk.
Just stumbled on this discussion. I know zilch about iotp, and no more
than epsilon about xml. So let me recap and see if I understand the
Something arrives described as application/iotp (or is it text/iotp - who
If you were expecting such things, and are in the business of handling
iotp objects (whatever they are), you presumably possess an iotp engine,
and have configured your mailer to use it when it sees application/iotp.
So far so good. But if you are not expecting such messages, you might like
to try to understand it to find out what is going on. If the best your
mailer can do is put it in a file and tell you it as recevied an
application/octet-stream, that leaves you on your own to figure it out.
But (so I gather) help is at hand. Iotp can also be understood by an XML
engine, which, even if it doesn't understand iotp fully, can at least
print out the structure of the document, so you know where to start
looking in order to figure it out.
So, what the message needs to say is "if you have an iotp engine, then
that should be the first choice for interpreting this document; but if
not, give it to your XML engine, which will at least have an intelligent
try". Is that correct?
If so, then surely the correct MIME way to do it is something like:
Content-Type: application/iotp; alternative-format=xml
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Email: chl(_at_)clw(_dot_)cs(_dot_)man(_dot_)ac(_dot_)uk Web:
Voice/Fax: +44 161 437 4506 Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5