Re: [ebxml-bp] ebBP 5/30/2005: Optional Business Transactions

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

Note: This is actually wd-2-0-1-02. Sorry.

> In Tuesday's call we discussed the optional transactions use case from 
> Cristiano Novelli.  See references below. Given our discusssion, I 
> have proposed a minor descriptive change as indicated in meeting 
> minutes (see resolution under this item). The change proposed is:
>
> Add after Table 7 in Section 3.4.11.1:
>
>    Forks and joins are useful particularly when activities between
>    parties may be optional.  For example, in retail or
>    manufacturing/production cases, order status may or may not occur.
>    However, when it does occur, the order response and status are
>    important to the involved parties.  In another case between a
>    Producer and a subcontractor, the order status, a disposition change
>    and response, and other integration changes may or may not occur.
>    In both cases, these optional business transactions may be modeled
>    as forks between the related business transactions.
>
> Reference:
>
wd-2-0-1-02!

>    * In comments list: wd-2-0-1-02 work item
>    * Novelli model description:
>      
> http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/email/archives/200505/msg00034.html 
>
>    * Novelli business scenario:
>      
> http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/email/archives/200505/msg00035.html 
>
>    * Meeting minutes reference, 24 May 2005:
>      
> http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/email/archives/200505/msg00033.html 
>
>
>