W3C home > Mailing lists > Public > xml-dist-app@w3.org > October 2002

Updated proposal for Issue 355 ( and 262 )

From: Martin Gudgin <mgudgin@microsoft.com>
Date: Tue, 29 Oct 2002 10:26:27 -0800
Message-ID: <92456F6B84D1324C943905BEEAE0278E02F4433F@RED-MSG-10.redmond.corp.microsoft.com>
To: <xml-dist-app@w3.org>

Revised proposal for Issue 355
I was given an action to revise the proposal[2] for Issue 355[1]
recently. Here is that revised proposal.
 
Proposal:
 
The intent of this proposal is to provide an infoset based description
of the rules already defined in section 2.6 and 2.7.1. It is not the
intent to change those rules. That is, the proposal is intended to
provide a "section 5" version of the "section 2" description. The
proposal can be incorporated somewhere in section 5 [4] as
appropriate:

1. Forwarding intermediaries MUST preserve all the infoset properties
    of soap:Body if forwarding with the exception of [base URI]
 
2. Forwarding intermediaries MUST preserve all the infoset properties
    of header blocks not targetted at them if forwarding with the
    exception of [base URI] 
 
2a. We will need to remove the sentence in 5.2.3[3] which says 
 'A SOAP intermediary MAY omit the SOAP mustUnderstand attribute
 information item if its value is "false"' 
 because that sentence is in conflict with 2. above. Given the way
 xmldsig works, dropping such attributes would break the signature,
 which we don't want to happen. We would also need to make the same 
 
3.  Forwarding intermediaries MAY change the value of the [children]
    property of soap:Envelope as follows:

 a) Forwarding intermediaries MAY remove whitespace character
 information items ( those whose [character code] property is #x20,
 #x9, #xD or #xA ) appearing in the [children] property of
 soap:Envelope. 
 
 b) Forwarding intermediaries MAY add ( or remove ) Comment
 Information Items to ( from ) the [children] property of
 soap:Envelope 

3.  Forwarding intermediaries MAY change the value of the [children]
    property of soap:Header as follows:
 
 a) They may and and/or remove EIIs from [children] as required by
 the header processing rules in [ref to processing model section
 for adding/removing header blocks]
 
 b) Forwarding intermediaries MAY remove whitespace character
 information items ( those whose [character code] property is #x20,
 #x9, #xD or #xA ) appearing in the [children] property of
 soap:Header.
 
 c) Forwarding intermediaries MAY add ( or remove ) Comment
 Information Items to ( from ) the [children] property of
 soap:Header.
 
4. Forwarding intermediaries MAY add attributes to the [attributes]
    property of both soap:Envelope and soap:Header. 
 
5. Forwarding intermediaries MUST preserve all other infoset of
    soap:Envelope and soap:Header with the exception of [base URI]
 
I consider all the above to be clarifications of the way our spec
works today. Essentially we don't constrain the structure or content
of the body or header blocks ( other than saying that PIs are not
allowed, which is covered elsewhere in the spec ). We allow
intermediaries to drop whitespace and/or comments appearing as
children of soap:Envelope and/or soap:Header.
 
As a secondary action, the editors need to go through Section 5[4] and
add some text either up-front or for each information item stating
which properties are NOT defined and/or constrained by our spec. My
preference would be to just have some text at the top of Section 5
that says something like: 
 
'Where a given property of an information item is not defined in this
section, this specification places no contraints on its value' 
 
Gudge
[1] http://www.w3.org/2000/xp/Group/xmlp-lc-issues.html#x355
[2] http://lists.w3.org/Archives/Public/xml-dist-app/2002Sep/0187.html 
[3] http://www.w3.org/2000/xp/Group/2/06/LC/soap12-part1.xml#soapmu
[4] http://www.w3.org/2000/xp/Group/2/06/LC/soap12-part1.xml#soapenv

 
Received on Tuesday, 29 October 2002 13:27:01 GMT

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