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


From: Mark Nottingham <mark.nottingham@bea.com>
Date: Thu, 8 May 2003 11:15:20 -0700
Message-ID: <013c01c3158d$fe7ad260$a502200a@mnotlaptop>
To: "John Kemp" <john.kemp@earthlink.net>, <xml-dist-app@w3.org>, "Paul Denning" <pauld@mitre.org>

Hi Paul,

First of all, application/rss+xml is not registered; it's merely an
Internet-Draft that I threw together one weekend.

RSS, GIF, JPEG, HTML and other versioned formats use common media types
because the are backwards-compatible; if a HTML2 engine receives an HTML4
document, it's expected to understand and render it to some degree. The
same situation exists with RSS, albeit with a much more liberal definition
of "understand", due to the somewhat rocky history of that format.

SOAP1.2 is not backwards-compatible with SOAP1.1; if a SOAP 1.1 processor
receives a SOAP1.2 message, it will fault. The fact that the protocol lets
nodes say "I don't understand that" (the VersionMismatch Fault) doesn't,
to me, imply that there is backwards-compatibility.

From RFC2048:

2.2.4.  Canonicalization and Format Requirements

   All registered media types must employ a single, canonical data
   format, regardless of registration tree.


----- Original Message ----- 
From: "Paul Denning" <pauld@mitre.org>
To: "John Kemp" <john.kemp@earthlink.net>; <xml-dist-app@w3.org>
Sent: Thursday, May 08, 2003 10:17 AM
Subject: Re: SOAP MIME Type

> At 05:08 PM 2003-05-07, John Kemp wrote:
> >2) What is the strategy for future versions of SOAP - will future
> >use a new MIME type each time, or will they continue to use that
> >in the SOAP 1.2 specification?
> Perhaps related is application/rss+xml, where a case is made to have
> media type apply to multiple versions of RSS [1].
> The IANA considerations section of [2] specifies an optional parameter:
> revision
>        The optional revision parameter indicates the integer version of
>        RSS used; the value is specified by the target RSS version.
> SOAP 1.2 [3] definition of application/soap+xml does not define a
> parameter.
> [1] http://groups.yahoo.com/group/rss-dev/message/5431
> [2] http://www.ietf.org/internet-drafts/draft-nottingham-rss2-00.txt
> [3] http://www.w3.org/TR/2003/PR-soap12-part2-20030507/#ietf-draft
> Paul
Received on Thursday, 8 May 2003 14:17:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:23 UTC