Marty:
RosettaNet PIPs conform to business transaction patterns defined in the UMM.
They make use of business signals (Receipt Acknowledgments) to indicate
successful receipt of business documents. Sometimes, the Receipt
Acknowledgment signal also serves the function of providing non repudiation
of receipt.
All asynchronous RosettaNet PIPs that I am aware of make use of Receipt
Acknowledgments. The only synchronous PIP in existence, PIP2A9, fits into
the UMM query-response pattern, so there is a synchronous response.
When using BPSS to model binary collaborations, transitions and guards
govern the order in which BusinessTransactionActivities are executed.
Typically, one BusinessTransactionActivity would have to be successfully
executed before another one is started (except when the fork construct is
used).
If the RequestingBusinessActivity and/or RespondingBusinessActivity within a
BusinessTransactionActivity specifies a timeToAcknowledgeReceipt, then
ReceiptAcknowledgments will have to be used and the
BusinessTransactionActivity cannot be considered successful until the
Receipt Acknowledgment has been returned.
With UMM and BPSS, it is possible to design BusinessTransactionActivities
that have no business level signals/responses (especially when there are no
NRR requirements). In practice, all RosettaNet PIPs have business level
signals/responses.
Regards,
-Arvola