W3C home > Mailing lists > Public > www-tag@w3.org > September 2003

Re: Requesting a revision of RFC3023

From: <noah_mendelsohn@us.ibm.com>
Date: Fri, 19 Sep 2003 11:04:11 -0400
To: MURATA Makoto <murata@hokkaido.email.ne.jp>
Cc: ietf-xml-mime@imc.org, WWW-Tag <www-tag@w3.org>
Message-ID: <OFF35186E2.2AF6FFA7-ON85256DA6.00528EF2@lotus.com>

Murata Makoto writes:

>> I believe that SOAP implementations use the 
>> charset parameter.  If we remove the charset 
>> parameter, we will make them non-conformant.

This is not my area of expertise, but I note that the HTTP binding [1] 
provided by SOAP 1.2 Recommendation uses an application/soap+xml media 
type, a definition of which is at [2] (I believe it is working its way 
through the formal registration process.)  My reading is that the 
definition lists charset as optional, and makes clear that its proper use 
is to be found in RFC 3023. 

I am not aware of what typical implementations of SOAP 1.1 or SOAP 1.2 are 
doing, but the 1.2 spec at least seems to list it as optional.  Again, I'm 
not expert in this stuff and am not offering an opinion, but I thought the 
links might be helpful.

[1]http://www.w3.org/TR/soap12-part2/#soapinhttp
[2] http://www.w3.org/TR/soap12-part2/#ietf-draft

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







MURATA Makoto <murata@hokkaido.email.ne.jp>
Sent by: www-tag-request@w3.org
09/19/03 08:10 AM

 
        To:     ietf-xml-mime@imc.org, WWW-Tag <www-tag@w3.org>
        cc:     (bcc: Noah Mendelsohn/Cambridge/IBM)
        Subject:        Re: Requesting a revision of RFC3023




On Fri, 19 Sep 2003 03:50:11 +0200
Bjoern Hoehrmann <derhoermi@gmx.net> wrote:

> You want to change something that has been STRONGLY RECOMMENDED for over
> five years to (ideally) MUST NOT just because it could cause trouble
> when used improperly or with broken implementations. Today I am good
> with web standards if I use the charset parameter, tommorow I am bad
> with web standards if I do. What's next on #W3C? Use tables for layout
> because people could get CSS wrong and old browsers get some CSS wrong?
> I don't think this leads anywhere.

I believe that SOAP implementations use the charset parameter.  If we 
remove the charset parameter, we will make them non-conformant.

Cheers,

-- 
MURATA Makoto <murata@hokkaido.email.ne.jp>
Received on Friday, 19 September 2003 11:05:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:20 GMT