W3C home > Mailing lists > Public > xml-dist-app@w3.org > May 2003

SOAP MIME Type

From: John Kemp <john.kemp@earthlink.net>
Date: Wed, 7 May 2003 17:08:57 -0400
To: xml-dist-app@w3.org
Message-Id: <1E0D3B70-80D0-11D7-BBAD-0003936AD1C2@earthlink.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

At Project Liberty, we have recently defined a 'Reverse HTTP Binding 
for SOAP' (also know as PAOS) It is called that because it binds a SOAP 
Request to an HTTP Response, and vice-versa.

We have been eyeing the application/soap+xml MIME type as a simple 
method for implementors of our specification to determine that a SOAP 
message was being sent. Given the status of SOAP 1.2, we had decided 
some time ago to normatively refer to SOAP 1.1 in our specifications.

I gather that only SOAP 1.2 envelopes may carry the 
application/soap+xml MIME type, and I was wondering if:

1) It would be possible to define the type so as to clearly not 
preclude the sending of SOAP 1.1 envelopes with that MIME type

And if not,

2) What is the strategy for future versions of SOAP - will future 
versions use a new MIME type each time, or will they continue to use 
that defined in the SOAP 1.2 specification?

Thanks in advance for any guidance you might give me,

- - JohnK
________________________________
John Kemp / john.kemp@earthlink.net
(+1) 413.458.9053    /    frumioj@AOL
Coordinating Editor   /   Project Liberty
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (Darwin)

iD8DBQE+uXXtn677NT86+ZsRAolUAKCB2v43qE8nbT+kAHZyHFDvniqbjwCeLMnx
jKyo8gTtSQbTaVAnP5+hepU=
=xT/Z
-----END PGP SIGNATURE-----
Received on Wednesday, 7 May 2003 17:08:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:14 GMT