some Version 3.0 comments

A few editorial comments:

 

L233: add "the": "On the
one hand..."

 

L265: "ebMS relies on a concept of
"Agreement" the concrete representation of..."

to replace with:

ebMS relies on a concept of Operation
COntext, which is 

normally derived from an
"Agreement" between partners, the concrete representation of... 

 

L291: remove  the almost empty
"Terminology" section 1.4 (redundant)

 

L330: define actors URIs (IRIs?) for ebXML
headers.

 

L451:

In case no message is available for
pulling, a SOAP Response is returned with an

ebMS error signal of severity level
"warning" that indicates an "empty queue".

replace with:

In case no message is available for
pulling, an eb:Error element with...(EmptyQueue)...  is generated. 

This element must be reported within the
SOAP Response".

 

L470: rephrase as: "One pipe, called
the default pipe, is always supported between

 a pair of communicating MSHs,
simply..."

 

L582: operation context: six main entities
(not five)

 

L2093: (e.g., in case the Reliability
sending module relies on its container entity -

here the MSH - for assigning valid
messages to sequences).

replace with:

(e.g., in case the container entity of the
Reliability sending module  -

here the MSH - has the responsibiity of
assigning messages to valid sequences, 

then it must be aware of invalid sequence
failures).

 

 

L2111: "...the Fault reporting action
if other actions are sufficient.

"replace with:

the Fault reporting action if other
reporting actions are sufficient.

 

L2123: replace:

"This specification is mostly

concerned with specifying this eb:Error
element, as well as how it is packaged in an eb:Message when

reported that way, because this is the
minimal requirement for error interoperability."

with:

"This specification is mostly
concerned with the minimal requirement for error interoperability, which is

about the possible contents of the
eb:Error element, as well as how it is packaged in an eb:Message when

reported that way.

"