
Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.8p1/8.12.8) with ESMTP id h3ILBKt2038118 for <ietf-xml-mime-bks@above.proper.com>; Fri, 18 Apr 2003 14:11:20 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.8p1/8.12.9/Submit) id h3ILBKMk038117 for ietf-xml-mime-bks; Fri, 18 Apr 2003 14:11:20 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f
Received: from lotus.lotus.com (lotus.lotus.com [129.42.250.41]) by above.proper.com (8.12.8p1/8.12.8) with ESMTP id h3ILBFt2038100 for <ietf-xml-mime@imc.org>; Fri, 18 Apr 2003 14:11:15 -0700 (PDT) (envelope-from noah_mendelsohn@us.ibm.com)
Received: from internet1.lotus.com (internet1 [172.16.131.235]) by lotus.lotus.com (8.12.9/8.12.6) with ESMTP id h3IL4wfx020261; Fri, 18 Apr 2003 17:04:58 -0400 (EDT)
Received: from cammail06.lotus.com (cammail06.lotus.com [9.33.9.29]) by internet1.lotus.com (8.12.9/8.12.6) with ESMTP id h3ILB4PC000917; Fri, 18 Apr 2003 17:11:04 -0400 (EDT)
To: Yves Lafon <ylafon@w3.org>
Cc: ietf-types@iana.org, ietf-xml-mime@imc.org, xml-dist-app@w3.orgb
Subject: Re: Please review ietf-draft of the "application/soap+xml" media type
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
From: noah_mendelsohn@us.ibm.com
Message-ID: <OF485C343B.5E8E4A66-ON85256D0C.00727DCB@lotus.com>
Date: Fri, 18 Apr 2003 17:03:38 -0400
X-MIMETrack: Serialize by Router on CAMMAIL06/CAM/M/Lotus(Release 6.0|September 26, 2002) at 04/18/2003 05:03:36 PM, Serialize complete at 04/18/2003 05:03:36 PM
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

I think this is on the whole just fine.  The sentence referenced below is 
(a) a run on sentence and (b) seems to imply that the media type is only 
useable in the context of a SOAP binding.  Isn't this a bit like saying 
that image/gif is only a useful media type if you have a GIF viewer 
application in mind?  It seems to me that the reference to SOAP bindings 
might be included as informative, but the media type is appropriate any 
time something is intended to be a SOAP envelope.  That could include one 
queued in a database, set out in a buffer or whatever.  Using this media 
type says:  this data is interpretable as a serialized SOAP envelope. 

<original>
This specification defines the media type "application/soap+xml" which can 
be used to identify SOAP messages serialized with XML 1.0 carried in MIME 
or MIME like protocols that support the concept of media types for which a 
SOAP binding has been defined.
</original>

<proposedShort>
This specification defines the media type "application/soap+xml" which can 
be used to identify SOAP message envelopes that have been serialized with 
XML 1.0. 
</proposedShort>


<proposedLonger>
This specification defines the media type "application/soap+xml" which can 
be used to identify SOAP message envelopes that have been serialized with 
XML 1.0.    Such serializations are useful as the basis "wire formats" for 
SOAP 1.2 Protocol Binding Specifications [ref to SOAP part 1 Section 4], 
or in other situations where an XML serialization of a SOAP envelope is 
required.
</proposedLonger>

I didn't mention MIME protocols as I assumed that the useability with MIME 
is implicit in defining any media type.  If not, one could put that back 
in too.  Thank you.

------------------------------------------------------------------
Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
------------------------------------------------------------------



