Proposed wording for issue 201

[Doug Bunting <Doug.Bunting@Sun.COM>]

My apologies for the many updates to the proposal for this issue as we 
were working today.

The issue presently includes the following:
	<proposal>s/Post/Post if the message is processed by an
	ebXML MSH handler/<br />Proposed update for lines 2555 -
	2558: s/If the <b>syncReplyMode</b> has a value of
	<b>none</b>, ... Post./If the <b>syncReplyMode</b> has a
	value of <b>none</b> and processing of the inbound ebXML
	message does not result in a SOAP Fault or (web server
	detected) HTTP error, ... Post.  The MSH MUST not insert
	content in the HTTP response (except SOAP Fault as
	described in the previous section) when
	<b>syncReplyMode</b> has the value <b>none</b>./</proposal>

OK, so the HTML may be more readable :)  The "proposed update" is what 
we were discussing today.  I am no longer suggesting an incomplete 
addition to the end of the sentence (which would result in that sentence 
having two "if" clauses and does not cover error situations the MSH may 
detect).  The additional restrictions now come at the beginning of the 
sentence which describes the expected message, providing a wire level 
perspective.  Adding an additional sentence to the end of the paragraph 
was Dale's good idea.  It adds an additional, implementation, perspective.

	Proposal: s/Post/Post if the message is processed by an ebXML MSH handler/

	Proposed update for lines 2555 - 2558: s/If the syncReplyMode has a 
value of none, ... Post./If the syncReplyMode has a value of none and 
processing of the inbound ebXML message does not result in a SOAP Fault 
or (web server detected) HTTP error, ... Post. The MSH MUST not insert 
content in the HTTP response (except SOAP Fault as described in the 
previous section) when syncReplyMode has the value none./

By the way, I should be able to update the online version of our issues 
list later in the week.

thanx,
	doug