OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: ebBP 2/22/2005: Section 4.6.6.5 Mutual Exclusivity


Per our discussion today for a bit more descriptive detail, see below. 
Comments welcome and appreciated.

Section 4.6.6.5
Mutually exclusive reference on DocumentEnvelope

Change from:
Document Envelopes are named. There is always only one named Document 
Envelope for a Requesting Activity. There MAY be zero, one, or many 
mutually exclusive, named Document Envelopes for a Responding Activity. 
For example, the Response Document Envelopes for a purchase order 
transaction might be named PurchaseOrderAcceptance, PurchaseOrderDenial, 
and PartialPurchaseOrderAcceptance.
In the actual execution of the purchase order transaction, however, only 
one of the defined possible responses SHOULD be sent and the others 
SHOULD NOT occur. In the case of PartialPurchaseOrderAcceptance, 
multiple partial responses may be handled separately via the 
choreography. Choreography is discussed in more detail in section 4.6.7.1..

Change to:
Document Envelopes are named. There is always only one named Document 
Envelope for a Requesting Activity. There MAY be zero, one, or many 
mutually exclusive, named Document Envelopes for a Responding Activity. 
For example, the Response Document Envelopes for a purchase order 
transaction might be named PurchaseOrderAcceptance, PurchaseOrderDenial, 
and PartialPurchaseOrderAcceptance. If multiple document envelopes occur 
in the responding activity, only one will be used. The condition 
expressions assist in specifying how a particular DocumentEnvelope may 
be handled. Typically, different responses necessitate separate names 
that are identifiable by a NameID for reference. In the actual execution 
of the purchase order transaction, however, only one of the defined 
possible responses SHOULD be sent and the others SHOULD NOT occur. In 
the case of PartialPurchaseOrderAcceptance, multiple partial responses 
may be handled separately via the choreography. Choreography is 
discussed in more detail in section 4.6.7.1..




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]