ebBP 3/27/2005: Comment re: NOF Handoff (wd 10-schema 2/22)

["Monica J. Martin" <Monica.Martin@Sun.COM>]

Several emails were sent discussing backend processes. As we anticipate 
more changes will be required than advised in v2.0, I've proposed this 
change in addition to the others we have made thus far.  Proposed change:

Section 4.6.6.3
Change from: Criteria surrounding the use of the business transaction 
patterns may include reliable messaging and use of the 
isGuaranteedMessageDelivery requirement (See Section 4.6.6.1).  In 
preceding technical specification versions, the guiding principles used 
were incomplete in describing the scope and operational details related 
to state synchronization.

Change to: Criteria surrounding the use of the business transaction 
patterns may include reliable messaging and use of the 
isGuaranteedMessageDelivery requirement (See Section 4.6.6.1).  Any 
agreement between trading partners could specify that the 
certificate-based digest used by a message protocol could be captured 
and stored as the non-repudiation digest (making the message receipt 
function as a business protocol receipt). By default the Receipt 
Acknowledgement (and its associated on-repudiation attributes) are 
separate from the reliable messaging layer. In preceding technical 
specification versions, the guiding principles used were incomplete in 
describing the scope and operational details related to state 
synchronization.