TBTF: Editors action item on issue 197 (fwd)

-- 
Yves Lafon - W3C
"Baroula que barouleras, au tiéu toujou t'entourneras."

---------- Forwarded message ----------
Date: Mon, 15 Apr 2002 15:43:09 +0100
From: Marc Hadley <marc.hadley@sun.com>
To: w3c-xml-protocol-wg@w3.org
Subject: TBTF: Editors action item on issue 197
Resent-Date: Mon, 15 Apr 2002 10:43:51 -0400 (EDT)
Resent-From: w3c-xml-protocol-wg@w3.org

All,

The editors took an action item to "come up with wording for intro (7.1)
and the two tables to incorporate our general agreed upon understanding
of the resolution to 197"

Here's an attempt to do that.

Section 7.1

Current text:

"HTTP applications MUST use the media type "application/soap+xml"
according to [12] when including SOAP 1.2 messages in HTTP exchanges.
See [12] for parameters defined by this media type and their recommended
use."

Proposed replacement:

"Conforming implementations of this binding:

1. MUST be capable of sending and receiving messages serialised using
media type application/soap+xml whose proper use and parameters are
described in [12].

2. MAY send requests and responses using other media types providing
that such media types provide for at least the transfer of SOAP XML Infoset.

3. MAY, when sending requests, provide an HTTP Accept header. This header:

   (i)  SHOULD indicate an ability to accept at minimum
        application/soap+xml

   (ii) MAY additionally indicate willingness to accept other media
        types that satisfy 2 above."


Section 7.4.1.1, Table 9: HTTP Request Fields

Replace existing row:

"Content-Type header: "application/soap+xml" (see 7.1 Introduction)"

with

"Content-Type header: The media type of the request body, see 7.1
Introduction for a description of permissible media types."

Insert new row directly after this row:

"Accept header (optional): List of media types that are acceptable in
response to the request message."

Replace existing row:

"HTTP entity body: XML 1.0 serialisation of the SOAP message XML Infoset
carried in the context:CurrentMessage property of the message exchange
context. This binding mandates support for UTF-8 and UTF-16."

with

"HTTP entity body: SOAP message serialised according to the rules for
carrying SOAP messages in the media type given by the Content-type
header. Rules for carrying SOAP messages in application/soap+xml are
given in [12]"

section 7.4.1.3, table 12: State Description: Receiving

Current description:

"Receive HTTP response entity body, which is assumed to be a SOAP
envelope serialized according to XML 1.0."

Proposed replacement:

"Receive HTTP response entity body, which is assumed to be a SOAP
envelope serialized according the rules carrying SOAP messages in the
media type given in the Content-type header."

section 7.4.2.1, table 17: HTTP Response Headers

Replace row:

"Content-Type: "application/soap+xml" (see 7.1 Introduction)"

with:

"Content-Type header: The media type of the response body, see 7.1
Introduction for a description of permissible media types."

Comments ?
Marc.

-- 
Marc Hadley <marc.hadley@sun.com>
XML Technology Centre, Sun Microsystems.

Received on Thursday, 25 April 2002 08:30:35 UTC