CD 2 - edits

[Ric Emery <remery@cyclonecommerce.com>]

Title: CD 2 - edits

A)
3.1 - Processing Mode Features

The P-Mode is partitioned into six functional groups called P-Mode features. Each P-Mode feature covers one of the six functional areas that is critical to achieving interoperability between two partners: security, reliability, transport, business collaboration, error reporting, Message Exchange Patterns and Message Partition Flows.

The text discusses six groups and six features, but then goes on too list seven functional areas. Seems a bit inconsistent.

--
B)
643 – P-Mode.businessCollaboration – It also indicates which MEPs and which MPFs are to be used by these parties.

The next line – 644 – dicusses P-Mode.messagePartitionFlows. Should the discussion about MPFs be removed from line 643?

----
C)
Figure 7: Should the term Pipe be removed from the figure?

-----
D)
The examples in section 4 and section 5 use the “SOAP” namespace prefix. The examples should be modified to use the S11 or S12 namespace prefix.

------
E)
Figure 7 and Figure 8 refer to the wss namespace prefix. The figures should be updated to refer to the wsse namespace prefix.

------
F)
7.3 ebMS Error Message
I do not think the text is very clear in regards to when eb:MessageInfo/eb:RefToMessageId should be relied upon to link errors to messages. Vs. when eb:Error/@refToMessageInError should be used.
The sentence at line 2205 throws me off a bit.
    If the element eb:SignalMessage/eb:MessageInfo does not contain eb:RefToMessageId, then the eb:Error element MUST NOT be related to a particular ebMS Message.