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

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

From: Larry Masinter <lmnet@attglobal.net>
Date: Tue, 26 Dec 2000 15:59:24 -0800
To: "Andrew Layman" <andrewl@microsoft.com>, <xml-dist-app@w3.org>
Message-ID: <NDBBKEBDLFENBJCGFOIJIEOPEBAA.lmnet@attglobal.net>
 > I have not seen a reply regarding the points below.  Modestly, I think they
> are good points and quite relevant to the continuing discussion, so I bring
> them to your attention again.

Here is a reply; I don't think this is a new reply, but it summarizes
replies made before.

> 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.

There are many problems that using "application/soap+xml" or
"application/xp+xml" as the Content-Type of SOAP/XP messages does not solve,
but that doesn't mean that they aren't the most appropriate Content-Type
to use.

In this case, I don't know what it would mean to "tie" the Content-Type
to a "URI" or what requirement would lead one to believe that XP should
be described in a decentralized way, or in a way that the content-type
itself were more extensible than the existing extensibility of using
content-types (namely, that anyone who wanted to define the 'scrub' protocol
could register application/scrub+xml and use it instead of

There are some elements of what it means to "speak XP" that need to
be agreed upon in order to have minimal interoperability. That's why
there's a standards group, rather than having each vendor go off
and implement their own thing and just forget about this mailing list.

The only question before us is "what content-type do we use when we
are using XML as agreed upon by this standards group", and the proposal
is to define one (say, application/xp+xml) specifically for that purpose.
This would allow one, for example, to distinguish "XP" from "SOAP/1.1"
and any of a dozen other protocols that operate by POSTing text/xml
bodies. The role of "Content-Type" in Internet protocols layered on
MIME is relatively minimal, but worth getting right.

If there is some other problem we should also be solving, could you
please elaborate?

> 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,

Of course. It's only that it seems fair, as you are reviving points
previously, to note that the responses were also given previously.

> 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.

I don't think we have any way to take "the essense of the idea" and
create a concrete proposal that is also consistent with the way that
MIME media types are actually defined and used. As you point out, there
are already multiple mechanisms in place for extensibility. The only role
of the "content-type" at all in XP is to distinguish XP traffic from
other traffic that might otherwise inadvertently traverse the same
transport/transfer protocol path.

> 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?

The important way in which existing implementations are considered is
to keep out of their way, and vice-versa. Not just "existing implementations
of SOAP, ebXML, WebDAV", etc., but existing implementations of MIME

Were XP to be transport over something other than HTTP, a "content-type"
parameter might not be necessary at all.
Received on Tuesday, 26 December 2000 19:00:44 GMT

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