Transaction States

There are 30 specific recommendations in the "Specific Recommendations" section of the submitted Hammerstrom paper. I have numbered them all for traceability as I recombine them into specific issues. The original white paper/submission can be read in the URI under "environment"

24. Section 8: This section points out the weakness of using transaction and Transaction differently. I liked the use of Transaction in TEMIX as a state of a transaction. All this subtle distinction is lost if capitalization is not used consistently, as is the case in this section. 

26. Table 9-2: I think the fact that an EiTransaction always has Transactive State=transaction is a vestige of an earlier, preferable approach. Wouldn’t it be much more elegant to define a single transaction behavior, in which the transaction migrates through its available states? Each of the Tender Facet, Transaction Facet (and possibly Quote Facet) should be defined as state transition behaviors, but I question why the structure of the interaction payloads should differ at all.  

• Tender, Transaction, Delivery, (Quote) address states of an interaction and were more clearly addressed by a TEMIX enumeration. This may be an unwise simplification, as it limits future extension of interaction attributes.