Section 2.5.2.3 Interaction Syntax

"   <record  name="ncname"
            when="before"|"after"|"timeout"
            causeException="true"|"false"? >
     <source  variable="XPath-expression"? | 
expression="Xpath-expression"? />
     <target  variable="XPath-expression" />
   </record>*
"
Suggestion: The definitions of successul-sending and properly-received 
is vital to any legally relevant communication specification 
mechansimssuch as CDL (see above refs). By defining *events* for when a 
data message ha been sent and receive, an important level of precision 
is achieved. The exact definition of successful reception is not only a 
technical problem but more importantly also a legal issue. A simple 
mechanism is to explicitly define the 4 Events and relate Interaction 
completions and variable binding to the events. Organisations such 
UN/CEFACT and national bodies can then apply their specific definitions 
of succesful-reception etc.

The suggestion seem easilly implementable without changing the CDL 
semantics and CDL usefulness and appropriatness for eCommerce will increase.

Adding (4 or more) Events-specifications to Recording and relate them to 
*when* be be an additions. There is a vital/key difference between 
*before* and *successful-sending* where usually the legal meaning is 
attached to *successful-sending*.

"
   <record  name="ncname"
            act="send"|"receive"
            when="before"|"after"|"timeout"
            causeException="true"|"false"? >
     <source  variable="XPath-expression"? | 
expression="Xpath-expression"? />
     <target  variable="XPath-expression" />

     <event name="ncname" act="send"|"receive" 
when="before"|"after"|"timeout"(|"exception")/>
         ... precise definitions added elsewhere ...
     </event>
   </record>*
"

It is important to, in the rest of the CDL document, be clear that the 
occurence of these events are the real trigges for variable assignements 
etc.