W3C home > Mailing lists > Public > xml-dist-app@w3.org > December 2000

RE: text/xml for SOAP (and XP) considered harmful

From: Andrew Layman <andrewl@microsoft.com>
Date: Wed, 13 Dec 2000 15:56:26 -0800
Message-ID: <C3729BBB6099B344834634EC67DE4AE1348FBF@red-msg-01.redmond.corp.microsoft.com>
To: xml-dist-app@w3.org
The proposal to use an elaborated form of Content-Type, e.g.
"application/soap+xml",  does not solve a major problem of content types,
namely that they are not tied in with URIs and consequently are not
manageable or extensible in a decentralized way.  

Regarding a specific proposal that would, in effect, use a URI in place of
"soap+" in the above example, MURATA Makoto wrote

"This has been already discussed in the IETF-XML-MIME mailing list, 
and has been turned down.  First, a document may contain more than 
one namespace.  Second, existing implementations of MIME does not 
use parameters."

Concentrating on the reasons given, which must be the reasons by which we
judge the proposal, and not on the fact that the point has been discussed
elsewhere, 

a.	The essence of the idea of using a URI in lieu of "+something" is
not that it must be the element name of the root element, but that it is an
identifier from the universal resource identifier namespace, and so operates
with the same decentralized authority that has proved essential in URLs,
SOAPAction headers and XML Namespaces.

b.	Existing implementations should indeed be considered.  Is it
asserted that all existing implementations process
"application/something+xml" in the intended way?  Or is it asserted that
many existing implementations can be adapted to the more elaborated form of
content type, but cannot be adapted to use parameters?
Received on Wednesday, 13 December 2000 18:57:10 GMT

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